-
-
Notifications
You must be signed in to change notification settings - Fork 32.1k
bpo-41735: Fix thread lock in zlib.Decompress.flush() may go wrong #29587
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.
PR #29588 does this for 3.9; as the backport automation may fail for 3.9/3.8 I'll use that for those if necessary. |
Thanks @animalize for the PR, and @gpshead for merging it 🌮🎉.. I'm working now to backport this PR to: 3.8, 3.9, 3.10. |
Sorry, @animalize and @gpshead, I could not cleanly backport this to |
GH-29811 is a backport of this pull request to the 3.10 branch. |
Sorry @animalize and @gpshead, I had trouble checking out the |
…ythonGH-29587) * Fix thread lock in zlib.Decompress.flush() may go wrong Getting `.unconsumed_tail` before acquiring the thread lock may mix up decompress state. (cherry picked from commit 7edb627) Co-authored-by: Ma Lin <animalize@users.noreply.github.com>
…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>
…rong (GH-29587) (GH-29811) * Fix thread lock in zlib.Decompress.flush() may go wrong Getting `.unconsumed_tail` before acquiring the thread lock may mix up decompress state. (cherry picked from commit 7edb627) Co-authored-by: Ma Lin <animalize@users.noreply.github.com> Automerge-Triggered-By: GH:gpshead
https://bugs.python.org/issue41735