fix mis-sizing of string in jbuf implementation #1353
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
Any time the jbuf string grows, the head of the jbuf must be accounted for. This patch fixes that oversight. The oversight leads to writing past the end of the string after it is expanded.
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.
Any time the jbuf string grows, the head of the jbuf must be accounted for. This patch fixes that oversight. The oversight leads to writing past the end of the string after it is expanded. Any code publishing large messages assembled with jbuf_t is subject to memory corruption if it writes in the last 16 bytes of the space believed to be available when they in fact aren't.
cherry picked for top of tree from 40ebe9b