diff options
author | Luiz Capitulino <lcapitulino@redhat.com> | 2012-05-11 16:19:46 -0300 |
---|---|---|
committer | Michael Roth <mdroth@linux.vnet.ibm.com> | 2012-05-15 09:15:16 -0500 |
commit | dc8764f06155a7b3e635e02281b747a9e292127e (patch) | |
tree | 7191954c7f6d4157e6f98c869344c1d065084017 /fpu | |
parent | 226a48949cf74006a94b5931e50352b2af801ac7 (diff) | |
download | qemu-dc8764f06155a7b3e635e02281b747a9e292127e.zip qemu-dc8764f06155a7b3e635e02281b747a9e292127e.tar.gz qemu-dc8764f06155a7b3e635e02281b747a9e292127e.tar.bz2 |
qemu-ga: guest-suspend: make the API synchronous
Currently, qemu-ga has a SIGCHLD handler that automatically reaps terminated
children processes. The idea is to avoid having qemu-ga commands blocked
waiting for children to terminate.
That approach has two problems:
1. qemu-ga is unable to detect errors in the child, meaning that qemu-ga
returns success even if the child fails to perform its task
2. if a command does depend on the child exit status, the command has to
play tricks to bypass the automatic reaper
Case 2 impacts the guest-suspend-* API, because it has to execute an external
program to check for suspend support. Today, to bypass the automatic reaper,
suspend code has to double fork and pass exit status information through a
pipe. Besides being complex, this is prone to race condition bugs. Indeed,
the current code does have such bugs.
Making the guest-suspend-* API synchronous (ie. by dropping the SIGCHLD
handler and calling waitpid() from commands) is a much simpler approach,
which fixes current race conditions bugs and enables commands to detect
errors in the child.
This commit does just that. There's a side effect though, guest-shutdown
will generate zombies if shutting down fails. This will be fixed by the
next commit.
Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
Diffstat (limited to 'fpu')
0 files changed, 0 insertions, 0 deletions