On 26.02.2026 23:01, Kevin Wolf wrote:
Am 26.02.2026 um 15:37 hat Hanna Czenczek geschrieben:
On 08.12.25 09:55, Dmitry Guryanov wrote:
Details: https://gitlab.com/qemu-project/qemu/-/issues/3144
The function schedule_next_request is called with tg->lock held and
it may call throttle_group_co_restart_queue, which takes
tgm->throttled_reqs_lock, qemu_co_mutex_lock may leave current
coroutine if other iothread has taken the lock. If the next
coroutine will call throttle_group_co_io_limits_intercept - it
will try to take the mutex tg->lock which will never be released.
...
This smells like a qemu-stable material (10.0.x, 10.1.x, 10.2.x).
Please let me know if it isn't.
Thanks,
/mjt
