[DRAFT] Remove OP-TEE TA TLS allocation#1032
Draft
sangho2 wants to merge 1 commit into
Draft
Conversation
sangho2
added
discussion
|
🤖 SemverChecks 🤖 No breaking API changes detected Note: this does not mean API is unchanged, or even that there are no breaking changes; simply, none of the detections triggered. |
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.
DRAFT
This PR removes the OP-TEE shim's guest TA allocation (i.e., no punchthrough). It assumes that TAs are built with patched
libuteeand entry function to configure thex86_64stack guard. For example, the AES TA test succeeds because it is rebuilt whereas the KMPP TA test fails (other two TAs don't accessfsat all).Ref: https://github.com/MSRSSP/op-tee-ia/blob/main/stack_guard.patch