multiprocessing.Event.set() can deadlock when called from a signal handler or trace function
Ninguém assumiu esta issue ainda.
- Linguagem predominante
- Python
- Estrelas
- 77.2k
- Forks
- 36k
- Métricas de merge de PRs
- Métricas de PR pendentes
Descrição
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
Guia de contribuição
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Direção de pesquisa
Comece em Lib/multiprocessing/synchronize.py pelos caminhos de is_set() e set() referenciados pelo stack trace e, em seguida, reproduza o problema com o programa de exemplo e o handler de sinal. Revise o PR vinculado gh-126437 e seus testes; considera-se concluído quando o Event não entrar mais em deadlock ao chamar set() a partir do handler ou da função de trace.
Escrita pelo modelo de indexação a partir do texto da issue.
Avaliação
- Stack de tecnologia
- python
- Domínio
- operating-systems
- Tipo de issue
- Bug
- Dificuldade
- 3/5
- Tempo estimado
- 1-2 dias
- Status de atividade
- Estagnada
- Clareza
- Claramente especificada
- Facilidade para iniciantes
- 25/100