]> git.ipfire.org Git - thirdparty/qemu.git/commit
futex: Check value after qemu_futex_wait()
authorAkihiko Odaki <akihiko.odaki@daynix.com>
Thu, 29 May 2025 05:45:50 +0000 (14:45 +0900)
committerPaolo Bonzini <pbonzini@redhat.com>
Fri, 6 Jun 2025 12:32:55 +0000 (14:32 +0200)
commit6e2d11bf04fb18e60afc8551871d9acb7b56983d
tree744dbbcb8debe3ef51de012bef56c1e732ab3481
parent4cdc489eb9c25f76255a550a4a0b19cda3435a76
futex: Check value after qemu_futex_wait()

futex(2) - Linux manual page
https://man7.org/linux/man-pages/man2/futex.2.html
> Note that a wake-up can also be caused by common futex usage patterns
> in unrelated code that happened to have previously used the futex
> word's memory location (e.g., typical futex-based implementations of
> Pthreads mutexes can cause this under some conditions).  Therefore,
> callers should always conservatively assume that a return value of 0
> can mean a spurious wake-up, and use the futex word's value (i.e.,
> the user-space synchronization scheme) to decide whether to continue
> to block or not.

Signed-off-by: Akihiko Odaki <akihiko.odaki@daynix.com>
Link: https://lore.kernel.org/r/20250529-event-v5-1-53b285203794@daynix.com
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
include/qemu/futex.h
tests/unit/test-aio-multithread.c
util/qemu-thread-posix.c