Use OPENSSL_zalloc in more places #1447
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
justsmth
force-pushed
the
zalloc-all-the-things
branch
from
77e6e1c
to
1d40d3e
Compare
justsmth
force-pushed
the
zalloc-all-the-things
branch
from
0997b97
to
38591dc
Compare
skmcgrail
reviewed
Feb 21, 2024
nebeid
approved these changes
Feb 22, 2024
skmcgrail
approved these changes
Feb 23, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of changes:
OPENSSL_zallocinstead ofOPENSSL_mallocwhen it makes subsequent initialization unnecessary.Call-outs:
OPENSSL_rezallocor modifyOPENSSL_reallocto callOPENSSL_zalloc, there's a couple more places where we might avoid subsequent initializations.Testing:
Debug/FIPS build succeeded on my Mac.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and the ISC license.