summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorVictor Stinner <vstinner@python.org>2023-10-05 18:53:03 (GMT)
committerGitHub <noreply@github.com>2023-10-05 18:53:03 (GMT)
commit318f5df27109ff8d2519edefa771920a0ec62b92 (patch)
tree0c38e6feb997021ec49437962cc92835eac1bdd7
parent1f3af03f83fead5cd86d54e1b2f47fc5866e635c (diff)
downloadcpython-318f5df27109ff8d2519edefa771920a0ec62b92.zip
cpython-318f5df27109ff8d2519edefa771920a0ec62b92.tar.gz
cpython-318f5df27109ff8d2519edefa771920a0ec62b92.tar.bz2
gh-110167: Fix test_socket deadlock in doCleanups() (#110416)
Fix a deadlock in test_socket when server fails with a timeout but the client is still running in its thread. Don't hold a lock to call cleanup functions in doCleanups(). One of the cleanup function waits until the client completes, whereas the client could deadlock if it called addCleanup() in such situation. doCleanups() is called when the server completed, but the client can still be running in its thread especially if the server failed with a timeout. Don't put a lock on doCleanups() to prevent deadlock between addCleanup() called in the client and doCleanups() waiting for self.done.wait of ThreadableTest._setUp().
-rw-r--r--Lib/test/test_socket.py12
-rw-r--r--Misc/NEWS.d/next/Tests/2023-10-05-19-33-49.gh-issue-110167.mIdj3v.rst5
2 files changed, 12 insertions, 5 deletions
diff --git a/Lib/test/test_socket.py b/Lib/test/test_socket.py
index 09605f7..0d1c186 100644
--- a/Lib/test/test_socket.py
+++ b/Lib/test/test_socket.py
@@ -218,8 +218,13 @@ class SocketUDPLITETest(SocketUDPTest):
class ThreadSafeCleanupTestCase:
"""Subclass of unittest.TestCase with thread-safe cleanup methods.
- This subclass protects the addCleanup() and doCleanups() methods
- with a recursive lock.
+ This subclass protects the addCleanup() method with a recursive lock.
+
+ doCleanups() is called when the server completed, but the client can still
+ be running in its thread especially if the server failed with a timeout.
+ Don't put a lock on doCleanups() to prevent deadlock between addCleanup()
+ called in the client and doCleanups() waiting for self.done.wait of
+ ThreadableTest._setUp() (gh-110167)
"""
def __init__(self, *args, **kwargs):
@@ -230,9 +235,6 @@ class ThreadSafeCleanupTestCase:
with self._cleanup_lock:
return super().addCleanup(*args, **kwargs)
- def doCleanups(self, *args, **kwargs):
- with self._cleanup_lock:
- return super().doCleanups(*args, **kwargs)
class SocketCANTest(unittest.TestCase):
diff --git a/Misc/NEWS.d/next/Tests/2023-10-05-19-33-49.gh-issue-110167.mIdj3v.rst b/Misc/NEWS.d/next/Tests/2023-10-05-19-33-49.gh-issue-110167.mIdj3v.rst
new file mode 100644
index 0000000..d0cbbf9
--- /dev/null
+++ b/Misc/NEWS.d/next/Tests/2023-10-05-19-33-49.gh-issue-110167.mIdj3v.rst
@@ -0,0 +1,5 @@
+Fix a deadlock in test_socket when server fails with a timeout but the
+client is still running in its thread. Don't hold a lock to call cleanup
+functions in doCleanups(). One of the cleanup function waits until the
+client completes, whereas the client could deadlock if it called
+addCleanup() in such situation. Patch by Victor Stinner.