-
Notifications
You must be signed in to change notification settings - Fork 6.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Coverity CID :219529] Unchecked return value in subsys/bluetooth/controller/ll_sw/ull_filter.c #32917
Comments
I couldn’t find any documentation for the mayfly code. https:/zephyrproject-rtos/zephyr/blob/master/subsys/bluetooth/controller/util/mayfly.c there are no doxygen comments in Seems to return I’m curious what a “mayfly” is 🤔 |
mayfly is an internal framework in the Bluetooth Low Energy Controller implementation to schedule a function's execution in a different execution context. It can be seen as a software interrupt mechanism. |
This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time. |
Explicitly ignore return value from call to mayfly_enqueue. Fixes zephyrproject-rtos#32917, zephyrproject-rtos#32961. Signed-off-by: Vinayak Kariappa Chettimada <[email protected]>
Explicitly ignore return value from call to mayfly_enqueue. Fixes #32917, #32961. Signed-off-by: Vinayak Kariappa Chettimada <[email protected]>
Static code scan issues found in file:
https:/zephyrproject-rtos/zephyr/tree/bd97359a5338b2542d19011b6d6aa1d8d1b9cc3f/subsys/bluetooth/controller/ll_sw/ull_filter.c#L1121
Category: Error handling issues
Function:
target_resolve
Component: Bluetooth
CID: 219529
Details:
zephyr/subsys/bluetooth/controller/ll_sw/ull_filter.c
Line 1121 in bd97359
Please fix or provide comments in coverity using the link:
https://scan9.coverity.com/reports.htm#v32951/p12996.
Note: This issue was created automatically. Priority was set based on classification
of the file affected and the impact field in coverity. Assignees were set using the CODEOWNERS file.
The text was updated successfully, but these errors were encountered: