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
Remove receiving of unused return value #23276
Conversation
CLA: trivial
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agree trivial
Wouldn't a better fix be to actually check the result of |
Actually function cannot cause an "insufficient buffer" failure due to check higher. In the case of an incorrect string literal specifying the format, the use of the information specified in the buffer will fail, for which there is a check below. Nevertheless, it might still be better to add a check for return codes. idk. |
I agree with @tom-cosgrove-arm |
This PR is in a state where it requires action by @openssl/committers but the last update was 30 days ago |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While it would definitely be better to add checks, rather than just omit them, the rest of the code in apps/
appears to be no better. Even in tests I see a TEST_true(BIO_snprintf(...))
(and that's insane, since BIO_snprintf()
returns number of chars written or -1 for error, so is presumably almost never going to return zero).
So I'm now approving this PR as-is - any further fixing would need to have a wider scope
This pull request is ready to merge |
Merged to the master branch. Thank you for your contribution. |
CLA: trivial Reviewed-by: Matt Caswell <matt@openssl.org> Reviewed-by: Tom Cosgrove <tom.cosgrove@arm.com> (Merged from #23276)
Found by Linux Verification Center (linuxtesting.org) with SVACE.
CLA: trivial