-
-
Notifications
You must be signed in to change notification settings - Fork 31.9k
gh-129732: Fix race in on shared->array in qsbr code under free-threa… #129738
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
Conversation
This LGTM, just needs a NEWS blurb |
…-threading. The read of shared->array should happen under the lock to avoid a race. Fixes python#129732
Done. I'm not sure how these normally look, let me know if you need something different. |
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.
Thanks!
Thanks @hawkinsp for the PR, and @colesbury for merging it 🌮🎉.. I'm working now to backport this PR to: 3.13. |
Sorry, @hawkinsp and @colesbury, I could not cleanly backport this to
|
GH-129747 is a backport of this pull request to the 3.13 branch. |
…r free-threading (pythongh-129738) The read of `shared->array` should happen under the lock to avoid a race. (cherry picked from commit b4ff8b2) Co-authored-by: Peter Hawkins <[email protected]>
…-threading (gh-129738) (gh-129747) The read of `shared->array` should happen under the lock to avoid a race. (cherry picked from commit b4ff8b2) Co-authored-by: Peter Hawkins <[email protected]>
|
The buildbot failure looks unrelated. The modified file is only used in the free threading build and the failed buildbot is for the default (GIL-enabled) build. EDIT: See #128381 |
…threading (pythongh-129738) The read of `shared->array` should happen under the lock to avoid a race.
…threading (pythongh-129738) The read of `shared->array` should happen under the lock to avoid a race.
…ding.
The read of shared->array should happen under the lock to avoid a race.
Fixes #129732