qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Michael Roth <mdroth@linux.vnet.ibm.com>
Cc: "pbonzini@redhat.com" <pbonzini@redhat.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v3] network scripts: don't block SIGCHLD before forking
Date: Thu, 08 Dec 2011 14:36:52 +0100	[thread overview]
Message-ID: <4EE0BD74.7000208@siemens.com> (raw)
In-Reply-To: <1323316087-1070-1-git-send-email-mdroth@linux.vnet.ibm.com>

On 2011-12-08 04:48, Michael Roth wrote:
> This patch fixes a bug where child processes of launch_script() can
> misbehave due to SIGCHLD being blocked. In the case of `sudo`, this
> causes a permanent hang.
> 
> Previously a SIGCHLD handler was added to reap fork_exec()'d zombie
> processes by calling waitpid(-1, ...). This required other
> fork()/waitpid() callers to temporarilly block SIGCHILD to avoid
> having the final wait status being intercepted by the SIGCHLD
> handler:
> 
> 7c3370d4fe3fa6cda8655f109e4659afc8ca4269
> 
> Since then, the qemu_add_child_watch() interface was added to allow
> registration of such processes and reap only from that specific set
> of PIDs:
> 
> 4d54ec7898bd951007cb6122d5315584bd41d0c4
> 
> As a result, we can now avoid blocking SIGCHLD in launch_script(), so
> drop that behavior.
> 
> Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
> ---
>  net/tap.c |    6 ------
>  1 files changed, 0 insertions(+), 6 deletions(-)
> 
> diff --git a/net/tap.c b/net/tap.c
> index 1f26dc9..6c27a94 100644
> --- a/net/tap.c
> +++ b/net/tap.c
> @@ -346,15 +346,10 @@ static TAPState *net_tap_fd_init(VLANState *vlan,
>  
>  static int launch_script(const char *setup_script, const char *ifname, int fd)
>  {
> -    sigset_t oldmask, mask;
>      int pid, status;
>      char *args[3];
>      char **parg;
>  
> -    sigemptyset(&mask);
> -    sigaddset(&mask, SIGCHLD);
> -    sigprocmask(SIG_BLOCK, &mask, &oldmask);
> -
>      /* try to launch network script */
>      pid = fork();
>      if (pid == 0) {
> @@ -378,7 +373,6 @@ static int launch_script(const char *setup_script, const char *ifname, int fd)
>          while (waitpid(pid, &status, 0) != pid) {
>              /* loop */
>          }
> -        sigprocmask(SIG_SETMASK, &oldmask, NULL);
>  
>          if (WIFEXITED(status) && WEXITSTATUS(status) == 0) {
>              return 0;

Looks sane.

Reviewed-by: Jan Kiszka <jan.kiszka@siemens.com>

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux

  reply	other threads:[~2011-12-08 13:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-08  3:36 [Qemu-devel] [PATCH] network scripts: don't block SIGCHLD before forking Michael Roth
2011-12-08  3:43 ` [Qemu-devel] [PATCH v2] " Michael Roth
2011-12-08  3:50   ` Michael Roth
2011-12-08  3:48 ` [Qemu-devel] [PATCH v3] " Michael Roth
2011-12-08 13:36   ` Jan Kiszka [this message]
2011-12-12  8:01   ` Paolo Bonzini
2011-12-15 18:09   ` Anthony Liguori

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4EE0BD74.7000208@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).