Conversation
added 7 commits
July 1, 2020 07:42
They create a fake program break that moves with calls to sbrk rather than actually moving the real program break. Attempts to access memory in the "new" region will still cause policy violations, as they are not tagged.
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.
Adds a wrapper around the
sbrksystem call that fakes the program break by basically just keeping track of where it is and moving the pointer assbrkis called. Wheneversbrkis called, if the request is to expand the available memory (even if it's to re-expand it after shrinking it), the AP will send a message to the PEX using the PIPE's mailbox mechanism, including an interrupt. The PEX is then expected to make any changes to the data TMT that are necessary.