Repository navigation
mpk: restore PKRU state when a fiber resumes execution - #7789
Merged
Merged
Conversation
Member
Author
|
This probably needs an |
Contributor
Subscribe to Label Actioncc @peterhuene DetailsThis issue or pull request has been labeled: "wasmtime:api"Thus the following users have been cc'd because of the following labels:
To subscribe or unsubscribe from this label, edit the |
alexcrichton
left a comment
Member
There was a problem hiding this comment.
Looks good to me 👍
With a test that fails without this change I think it's good-to-go.
Previously, when a fiber was suspended, other computation could change the PKRU state on the current CPU. This means that the fiber could be resumed with a different PKRU state. This could be bad, resulting in situations in which the fiber can access more memory slots than it should or cannot even access its own memory slots. This change saves the PKRU state prior to a fiber being suspended. When the fiber resumes execution, that PKRU state is restored.
This adds a test that alternately polls two Wasm instances in a loop. Since the instances are async, we can set up epochs to suspend each fiber as we iterate over a loop. Because we alternate between the two instances, it checks that `AsyncCx::block_on` has correctly restored the PKRU bits; otherwise we should see test failures. In the process of writing this test I discovered bytecodealliance#7942, which can be solved separately (it has to do with the interaction between memory images, _not_ used here, and MPK). prtest:full
Not all stores have protection keys and MPK is not always enabled. This change checks for these conditions before context-switching the PKRU bits.
abrown
marked this pull request as ready for review
February 15, 2024 02:29
abrown
requested review from
alexcrichton and
fitzgen
and removed request for
a team
February 15, 2024 02:29
alexcrichton
approved these changes
Feb 15, 2024
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.
Previously, when a fiber was suspended, other computation could change the PKRU state on the current CPU. This means that the fiber could be resumed with a different PKRU state. This could be bad, resulting in situations in which the fiber can access more memory slots than it should or cannot even access its own memory slots.
This change saves the PKRU state prior to a fiber being suspended. When the fiber resumes execution, that PKRU state is restored.