summary refs log tree commit diff stats
path: root/scripts/qapi-gen.py
diff options
context:
space:
mode:
authorMax Reitz <mreitz@redhat.com>2021-01-25 13:03:05 +0100
committerMax Reitz <mreitz@redhat.com>2021-01-26 14:36:37 +0100
commitf4be8225198c4616b391d13d4ba083bf40f3a0c9 (patch)
treeb71a95c2c77e697c02a84f46edeec8e9ca00181d /scripts/qapi-gen.py
parent59c9466d58a9280c9a6ceaa9f38537977eac85f9 (diff)
downloadfocaccia-qemu-f4be8225198c4616b391d13d4ba083bf40f3a0c9.tar.gz
focaccia-qemu-f4be8225198c4616b391d13d4ba083bf40f3a0c9.zip
coroutine-sigaltstack: Add SIGUSR2 mutex
Disposition (action) for any given signal is global for the process.
When two threads run coroutine-sigaltstack's qemu_coroutine_new()
concurrently, they may interfere with each other: One of them may revert
the SIGUSR2 handler to SIG_DFL, between the other thread (a) setting up
coroutine_trampoline() as the handler and (b) raising SIGUSR2.  That
SIGUSR2 will then terminate the QEMU process abnormally.

We have to ensure that only one thread at a time can modify the
process-global SIGUSR2 handler.  To do so, wrap the whole section where
that is done in a mutex.

Alternatively, we could for example have the SIGUSR2 handler always be
coroutine_trampoline(), so there would be no need to invoke sigaction()
in qemu_coroutine_new().  Laszlo has posted a patch to do so here:

  https://lists.nongnu.org/archive/html/qemu-devel/2021-01/msg05962.html

However, given that coroutine-sigaltstack is more of a fallback
implementation for platforms that do not support ucontext, that change
may be a bit too invasive to be comfortable with it.  The mutex proposed
here may negatively impact performance, but the change is much simpler.

Signed-off-by: Max Reitz <mreitz@redhat.com>
Message-Id: <20210125120305.19520-1-mreitz@redhat.com>
Reviewed-by: Laszlo Ersek <lersek@redhat.com>
Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Diffstat (limited to 'scripts/qapi-gen.py')
0 files changed, 0 insertions, 0 deletions