-
Notifications
You must be signed in to change notification settings - Fork 346
fix(payload): initialize prewarming state synchronously #7227
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚨 [SECURITY] Coordinator-thread worker state survives across payload builds
WorkerPool::initandpool.clear()broadcast only to Rayon-owned pool threads, butin_place_scopeallows the external calling thread to execute scoped jobs. A job on that caller lazily stores this build's EVM in the global worker TLS; cleanup does not clear it, so a later build on the same coordinator thread can reuse stale parent state/environment. Its replay may then be rejected as invalid, causing an otherwise valid payment transaction to be omitted from the payload.Recommended Fix:
Initialize and explicitly clear the external scope caller's worker slot for every build, with a barrier before jobs begin, or avoid global worker TLS for external scope participants and pass build-scoped state directly. Add a two-build regression test on the same coordinator thread with distinct contexts and force a scoped task onto that thread.