Fix IterMut Stacked Borrows violation#224
Merged
jeromefroe merged 2 commits intojeromefroe:masterfrom Jan 7, 2026
Merged
Conversation
Owner
|
Thank you @paolobarbolini! |
This was referenced Jan 7, 2026
|
Will there be a fix for 0.12.x and 0.13.x branches? Asking because of chatmail/core#7692 |
This was referenced Jan 8, 2026
This was referenced Feb 8, 2026
This was referenced Apr 13, 2026
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.
This fixes a Stacked Borrows violation in
IterMut. The issue was thatIterMut::nextandIterMut::next_backtemporarily create an exclusive reference to the key. This invalidates the pointer held withinKeyWrapperby theHashMap, but the HashMap still holds and accesses it on subsequent reads or writes to the LRU, which is unsound.The implementation silently coerces the esclusive reference into a shared reference, but this does not undo the effect of the exclusive reference.
This can be seen by running miri on the test that I've added in the second commit without the fix in the first commit.
The solution is to use shared references throughout, rather than first requesting an exclusive reference and then converting it into a shared reference.