-
-
Notifications
You must be signed in to change notification settings - Fork 32.1k
[3.9] bpo-41735: Fix thread lock in zlib.Decompress.flush() may go wrong #29588
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
Getting `.unconsumed_tail` before acquiring the thread lock may mix up decompress state.
A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated. Once you have made the requested changes, please leave a comment on this pull request containing the phrase |
PR #29587 takes care of this on |
Thanks @animalize for the PR, and @gpshead for merging it 🌮🎉.. I'm working now to backport this PR to: 3.8. |
GH-29812 is a backport of this pull request to the 3.8 branch. |
…ong (pythonGH-29588) * Fix thread lock in zlib.Decompress.flush() may go wrong Getting `.unconsumed_tail` before acquiring the thread lock may mix up decompress state. backport of python#29587 to 3.9/3.8. (cherry picked from commit 86c1265) Co-authored-by: Ma Lin <animalize@users.noreply.github.com>
For 3.9- branches.
https://bugs.python.org/issue41735