Skip to content

Satisfy the OP-TEE TA stack-guard read via the stack canary#1003

Open
sangho2 wants to merge 2 commits into
mainfrom
sanghle/optee/notls
Open

Satisfy the OP-TEE TA stack-guard read via the stack canary#1003
sangho2 wants to merge 2 commits into
mainfrom
sanghle/optee/notls

Conversation

@sangho2

@sangho2 sangho2 commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

This PR satisfies the OP-TEE TA's stack-guard read via the TA stack canary. Currently, the OP-TEE shim allocates a dummy TLS page to satisfy OP-TEE TA's stack-guard read (emitted by the x86_64 toolchain) even though TAs have no TLS (they are single-threaded). Instead of using such an extra page, this PR lets the stack-guard read resolve on the stack canary that the shim prepares.

@sangho2 sangho2 force-pushed the sanghle/optee/notls branch from 9a36d62 to e3d2fee Compare July 2, 2026 23:19
@sangho2 sangho2 force-pushed the sanghle/optee/notls branch from e3d2fee to 95eeab4 Compare July 2, 2026 23:33
@sangho2 sangho2 marked this pull request as ready for review July 2, 2026 23:45
@github-actions

github-actions Bot commented Jul 6, 2026

Copy link
Copy Markdown

🤖 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant