-
-
Notifications
You must be signed in to change notification settings - Fork 32.6k
gh-137583: Only lock the SSL context, not the SSL socket #137588
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
Merged
+60
−19
Merged
Changes from 14 commits
Commits
Show all changes
16 commits
Select commit
Hold shift + click to select a range
0a070e2
Only lock the SSL context, not the SSL socket.
ZeroIntensity 42a0351
Fix the test.
ZeroIntensity c776679
Fix race conditions in the test case.
ZeroIntensity 90d93c3
I now realize that approach was bad.
ZeroIntensity 7ea2613
Some other fixups.
ZeroIntensity 5ff4efc
I give up.
ZeroIntensity cf630d7
Stupid workaround.
ZeroIntensity f3ec86c
Add blurb.
ZeroIntensity 12a68a5
Fix blurb.
ZeroIntensity d45f6a8
Supposedly this *actually* fixes the blurb.
ZeroIntensity 6799b03
Avoid Sphinx references for the blurb.
ZeroIntensity 38e29f9
Fix race condition in the test case (for real this time).
ZeroIntensity 64f7480
Fix the blurb (hopefully for the last time).
ZeroIntensity 6da074e
Fix the Windows buildbots.
ZeroIntensity bb99322
Blurb fixup.
ZeroIntensity 36a4d66
Ugh.
ZeroIntensity 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
4 changes: 4 additions & 0 deletions
4
Misc/NEWS.d/next/Library/2025-08-09-08-53-32.gh-issue-137583.s6OZud.rst
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,4 @@ | ||
Fix a deadlock introduced in 3.13.6 when a call to | ||
:meth:`ssl.SSLSocket.recv <socket.socket.recv>` was blocked in one thread, while another | ||
attempted to call :meth:`ssl.SSLSocket.send <socket.socket.send>` to unblock it in another | ||
thread. | ||
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
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.
Uh oh!
There was an error while loading. Please reload this page.
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.
I'd simplify this as follows:
Indeed, the problem happens even without a dependency between
recv
andsend
.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.
I don't think we even need to mention
send
at all. Ifrecv
was blocked, it's not possible to access most methods on anSSLSocket
, because they'll also try to acquire that same lock.