On 2/3/26 12:42, Richard Henderson wrote:
On 1/27/26 01:16, Aleksandr Sergeev wrote:
By the spec, fork() copies only the thread which executes it.
So it may happen, what while one thread is doing a fork,
another thread is holding `clone_lock` mutex
(e.g. doing a `fork()` or `exit()`).
So the child process is born with the mutex being held,
and there are nobody to release it.
As the thread executing do_syscall() is not considered running,
start_exclusive() does not protect us from the case.
Resolves:https://gitlab.com/qemu-project/qemu/-/issues/3226
Signed-off-by: Aleksandr Sergeev<[email protected]>
---
linux-user/main.c | 2 ++
linux-user/syscall.c | 14 ++++++++++++++
linux-user/user-internals.h | 2 ++
3 files changed, 18 insertions(+)
Reviewed-by: Richard Henderson <[email protected]>
Queued, thanks.
r~
