Add a GuardedPageAllocator fuzz target. - #1055
Draft
copybara-service[bot] wants to merge 1 commit into
Draft
copybara-service[bot] wants to merge 1 commit into
copybara-service[bot] wants to merge 1 commit into
Conversation
Drives one allocator through allocation, deallocation, writes to live allocations, and mlock()/munlock()/mlockall()/munlockall() over the pages it has handed out. Locking constrains which operations the kernel permits on the pool's mapping, so the mechanism that quarantines a page and the one that releases it have to pair up however these are interleaved. Every allocation carries a fill pattern that is verified on each access and at deallocation. PiperOrigin-RevId: 985488098
This branch has not been deployed
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
1 participant
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.
Add a GuardedPageAllocator fuzz target.
Drives one allocator through allocation, deallocation, writes to live
allocations, and mlock()/munlock()/mlockall()/munlockall() over the pages it has
handed out. Locking constrains which operations the kernel permits on the
pool's mapping, so the mechanism that quarantines a page and the one that
releases it have to pair up however these are interleaved. Every allocation
carries a fill pattern that is verified on each access and at deallocation.