Repository navigation
multislab: separate iteration order from free-space lists - #9
Merged
aotodev merged 1 commit intoSep 29, 2026
Merged
Conversation
aotodev
deleted the
4-multislab-iteration-and-free-space-tracking-share-one-list
branch
September 29, 2026 17:58
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
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.
Iteration shared next/prev with the active/full lists, so moving a slab
between them sent live iterators into the wrong list: elements skipped
or visited twice, and a use-after-free once the captured full-list head
was released. Allocation also grew while slabs below the active head had
free slots, failing spuriously at a slab cap.
Each node now has a second link pair, relinked only on grow and free,
which the iterator follows. Slabs move to the full list on the
allocation that fills them, so every active slab has a free slot.
Closes #4