mapping_reuse: correct range size when unmapping failed allocations - #948
Closed
mateusz-bloch wants to merge 1 commit into
Closed
mateusz-bloch wants to merge 1 commit into
mateusz-bloch wants to merge 1 commit into
Conversation
|
|
|
This fix has been integrated locally in our development builds and will make it out in a future release. Thank you for your contribution. |
Collaborator
|
Thanks for the fix, @mateusz-bloch . Closing. |
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
4 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.
Fixes incorrect unmap range size in the error cleanup path of reusemappingdbMap().
Previously, range.size was used instead of the actual mapped fragment size (token.pList->size) when calling pUnmapCb. This could result in over-unmapping and overlapping VA ranges, causing inconsistencies and VA allocation failures.