Fix address-instability in MultiSegmentArena by storing *Segment and validating via (id, arena storage) #607
Conversation
This file contains hidden or 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
lthibault
approved these changes
Oct 24, 2025
|
Do I need to cut a release? |
|
Yes, I think so. This is due to previous version is buggy with MultiSegment. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 attempts to fix #606 -
MultiSegmentArena:preferred segment is not part of the arena[]Segmentwith[]*Segmentin MultiSegmentArena to avoid address-instability on append.Segment(id)return the stable pointer frommsa.segs(no&msa.segs[id]).Allocate, validate the preferred segment in O(1) by checkingseg.idis in-range andmsa.segs[seg.id] == seg; remove the linear pointer scan.msa.segslength in sync with the byte-storage (msa.segs[i].data).Release()zeroises and returns buffers, then clears pointers safely.