multiprocessing.Event.set() can deadlock when called from a signal handler or trace function
還沒有人認領這個 Issue。
- 主要語言
- Python
- 星號
- 77.2k
- 分支
- 35.9k
- PR 合併指標
- PR 指標待擷取
描述
Bug report
Bug description:
multiprocessing.Event.set() will acquire a lock when setting the internal flag. multiprocessing.Event.is_set() will acquire the same lock when checking the flag. Thus if a signal handler calls .set() when .is_set() is running on the same process, there will be a deadlock.
multiprocessing.Event uses a regular non-reentrantlock lock. This should be changed to a reentrant lock. Please see the pull request.
Thanks for all the work on the Python programming language. I appreciate all your efforts highly.
Kind regards.
Example program below that (sometimes) deadlocks. On my machine I typically need to run it less than 10 times before a deadlock occurs. Also included in the code block is a sample stacktrace.
import faulthandler
import multiprocessing
import os
import signal
def run_buggy():
shutdown_event = multiprocessing.Event()
def sigterm_handler(_signo, _stack_frame):
try:
print(f'sigterm_handler running')
shutdown_event.set()
finally:
print(f'sigterm_handler done')
signal.signal(signal.SIGTERM, sigterm_handler)
signal.signal(signal.SIGINT, sigterm_handler)
faulthandler.register(signal.SIGUSR1)
print(f'Running process with PID {os.getpid()}')
print(f'Dump the stack by executing:')
print(f'kill -SIGUSR1 {os.getpid()}')
print(f'Try to kill this process with CTRL-C or kill {os.getpid()}')
while not shutdown_event.is_set():
pass
if __name__ == '__main__':
run_buggy()
# Sample stacktrace:
# Current thread 0x00000001ed74cf40 (most recent call first):
# File "/Users/ire/code/cpython/Lib/multiprocessing/synchronize.py", line 95 in __enter__
# File "/Users/ire/code/cpython/Lib/multiprocessing/synchronize.py", line 237 in __enter__
# File "/Users/ire/code/cpython/Lib/multiprocessing/synchronize.py", line 342 in set
# File "/Users/ire/code/cpython/./bug.py", line 13 in sigterm_handler
# File "/Users/ire/code/cpython/Lib/multiprocessing/synchronize.py", line 95 in __enter__
# File "/Users/ire/code/cpython/Lib/multiprocessing/synchronize.py", line 237 in __enter__
# File "/Users/ire/code/cpython/Lib/multiprocessing/synchronize.py", line 335 in is_set
# File "/Users/ire/code/cpython/./bug.py", line 25 in run_buggy
# File "/Users/ire/code/cpython/./bug.py", line 29 in <module>
CPython versions tested on:
3.11, 3.12, CPython main branch
Operating systems tested on:
Linux, macOS
Linked PRs
- gh-126437
貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
研究方向
從 Lib/multiprocessing/synchronize.py 中 stack trace 引用的 is_set() 和 set() 路徑開始,然後使用範例程式和訊號處理常式重現該問題。檢查連結的 PR gh-126437 及其測試;當從處理常式或追蹤函式呼叫 set() 時 Event 不再死結,即表示完成。
由索引模型根據 Issue 內容生成。
評估
- 技術堆疊
- python
- 領域
- operating-systems
- Issue 類型
- 缺陷
- 難度
- 3/5
- 預估耗時
- 1-2 天
- 活躍度
- 停滯
- 描述清晰度
- 描述清楚
- 新手友好度
- 25/100