Branch: refs/heads/staging-10.2
Home: https://github.com/qemu/qemu
Commit: 1af52156676065b1fc2d4815bf23b1c4c99938b3
https://github.com/qemu/qemu/commit/1af52156676065b1fc2d4815bf23b1c4c99938b3
Author: Aleksandr Sergeev <[email protected]>
Date: 2026-02-10 (Tue, 10 Feb 2026)
Changed paths:
M linux-user/main.c
M linux-user/syscall.c
M linux-user/user-internals.h
Log Message:
-----------
linux-user/syscall.c: Prevent acquiring clone_lock while fork()
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]>
Reviewed-by: Richard Henderson <[email protected]>
Signed-off-by: Richard Henderson <[email protected]>
Message-ID: <[email protected]>
(cherry picked from commit d22e9aec572396836782e993cb18d598e6012688)
Signed-off-by: Michael Tokarev <[email protected]>
Commit: b5ce6809b4b47e6cd414c9ce9449b114cd5c657f
https://github.com/qemu/qemu/commit/b5ce6809b4b47e6cd414c9ce9449b114cd5c657f
Author: Paolo Bonzini <[email protected]>
Date: 2026-02-10 (Tue, 10 Feb 2026)
Changed paths:
M accel/tcg/cpu-exec.c
Log Message:
-----------
Revert "tcg/user: do not set exit_request gratuitously"
This reverts commit b422a7bff64eaf55b8250225533ca1df42c3777e.
The reporter says "The commit breaks go; if you run go build in a loop,
it eventually hangs uninterruptible (except -9) with a couple of zombie
children left over".
Reported-by: Andreas Schwab <[email protected]>
Signed-off-by: Paolo Bonzini <[email protected]>
Reviewed-by: Richard Henderson <[email protected]>
Signed-off-by: Richard Henderson <[email protected]>
Message-ID: <[email protected]>
(cherry picked from commit 251a3d4ca3c961d95cd624252a178a33066455a2)
Signed-off-by: Michael Tokarev <[email protected]>
Commit: 63a76e01238c8a3cc2c02f6a12ec53c2ab844a7a
https://github.com/qemu/qemu/commit/63a76e01238c8a3cc2c02f6a12ec53c2ab844a7a
Author: Andrey Drobyshev <[email protected]>
Date: 2026-02-10 (Tue, 10 Feb 2026)
Changed paths:
M scripts/qemugdb/timers.py
Log Message:
-----------
scripts/qemugdb: timers: Fix KeyError in 'qemu timers' command
Currently invoking 'qemu timers' command results into: "gdb.error: There
is no member named last". Let's remove the legacy 'last' field from
QEMUClock, as it was removed in v4.2.0 by the commit 3c2d4c8aa6a
("timer: last, remove last bits of last").
Signed-off-by: Andrey Drobyshev <[email protected]>
Reviewed-by: Stefan Hajnoczi <[email protected]>
Message-id: [email protected]
Signed-off-by: Stefan Hajnoczi <[email protected]>
(cherry picked from commit 80c97930a93c32e2e666f5420af2d5734021a135)
Signed-off-by: Michael Tokarev <[email protected]>
Compare: https://github.com/qemu/qemu/compare/ba31a6fca7b0...63a76e01238c
To unsubscribe from these emails, change your notification settings at
https://github.com/qemu/qemu/settings/notifications
