Fix buffer zeroing with offset in map_buffer #2916
Merged
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.
Checklist
cargo clippy
.Connections
None.
Description
The buffer zeroing code in
map_buffer
currently writes out of bounds if a non zero offset is passed.This is because the map_buffer code passes the
mapped_pointer + uninitialized.start
towrite_bytes
, however the uninitialized range is relative to the start of the buffer while our mapped pointer is offset.The offset parameter has to be subtracted from the uninitialized range so that the new range is relative to the mapped range and avoid (very scary) out of bounds writes.
Testing
None.