mirror of
https://github.com/python/cpython.git
synced 2025-08-03 08:34:29 +00:00
[3.11] gh-110167: Fix test_socket deadlock in doCleanups() (GH-110416) (#110424)
gh-110167: Fix test_socket deadlock in doCleanups() (GH-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().
(cherry picked from commit 318f5df271
)
Co-authored-by: Victor Stinner <vstinner@python.org>
This commit is contained in:
parent
8394368f1f
commit
8da3367067
2 changed files with 12 additions and 5 deletions
|
@ -204,8 +204,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):
|
||||
|
@ -216,9 +221,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):
|
||||
|
||||
|
|
|
@ -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.
|
Loading…
Add table
Add a link
Reference in a new issue