summaryrefslogtreecommitdiff
path: root/hw
diff options
context:
space:
mode:
authorDaniel P. Berrange <berrange@redhat.com>2015-08-28 14:40:01 +0100
committerDaniel P. Berrange <berrange@redhat.com>2015-10-20 14:40:49 +0100
commit57cb38b3833c5215131b983f181b26d6ba9b8d35 (patch)
treee277f087c5a7c2f9a4240637936a80e2b09f89be /hw
parente0d03b8ceb52e390b8b0a5db1762a8435dd8a44e (diff)
downloadqemu-57cb38b3833c5215131b983f181b26d6ba9b8d35.tar.gz
qemu-57cb38b3833c5215131b983f181b26d6ba9b8d35.tar.bz2
qemu-57cb38b3833c5215131b983f181b26d6ba9b8d35.zip
osdep: add qemu_fork() wrapper for safely handling signals
When using regular fork() the child process of course inherits all the parents' signal handlers. If the child then proceeds to close() any open file descriptors, it may break some of those registered signal handlers. The child generally does not want to ever run any of the signal handlers that the parent may have installed in the short time before it exec's. The parent may also have blocked various signals which the child process will want enabled. This introduces a wrapper qemu_fork() that takes care to sanitize signal handling across fork. Before forking it blocks all signals in the parent thread. After fork returns, the parent unblocks the signals and carries on as usual. The child, however, resets all the signal handlers back to their defaults before it unblocks signals. The child process can now exec the binary in a "clean" signal environment. Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
Diffstat (limited to 'hw')
0 files changed, 0 insertions, 0 deletions