-
Notifications
You must be signed in to change notification settings - Fork 224
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
Check Return Value for setsockopt #1172
Comments
hi i would like to work on this issue |
@himanshu007-creator Thank you for the participation! I assigned you to this issue. |
Fix nasa#1172, Update to use Ut_Stub_CheckDefaultReturnValue API
@ArielSAdamsNASA @himanshu007-creator - I'm not sure this solution solves an actual issue. This suggestion just does the same call again if the first fails which doesn't seem to be any better (odds are it'll just fail again). Although it is a static analysis warning, it's already documented (in comments) that if the call fails there isn't a need to take any further action. I'd recommend just closing this issue and the related pull request. |
Got it |
Describe the bug
Calling setsockopt(impl->fd, 1, 2, &os_flags, 4U) without checking return value. This library function may fail and return an error code.
Expected behavior
Check return value for setsockopt
Code snips
osal/src/os/portable/os-impl-bsd-sockets.c
Line 199 in 42af0f7
System observed on:
Coverity: https://scan.coverity.com/projects/arielsadamsnasa-cfs-jsf-rules?tab=overview
Additional context
Possible solution
Reporter Info
Ariel Adams, ASRC Federal
The text was updated successfully, but these errors were encountered: