Avoid buffer overflow in fillBufBuilderOne
#4
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.
This is nearly exactly the same fix as my last patch (#3), just for another occurrence of
Data.ByteString.Builder.More
. We haven't seen any issues resulting from this code path ourselves, but it is vulnerable to the same sort of buffer overflow as the previous patch (running a writer in a buffer which might not have enoughroom
).Sorry I missed this before! I bumped the version and added a ChangeLog entry.