From: Thiemo Seufer <ths@networkno.de>
To: Riku Voipio <riku.voipio@iki.fi>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] linux-user: Proper exit code for uncaught signals
Date: Thu, 27 Nov 2008 12:42:33 +0100 [thread overview]
Message-ID: <20081127114233.GC15592@networkno.de> (raw)
In-Reply-To: <20081123213724.GA15889@kos.to>
Riku Voipio wrote:
> The proper exit code for dieing from an uncaught signal is -<signal>.
> The kernel doesn't allow exit() or _exit() to pass a negative value.
> To get the proper exit code we need to actually die from an uncaught
> signal.
>
> A default signal handler is installed, we send ourself a signal
> and we wait for it to arrive.
>
> Patch originates from Scratchbox
So, who holds the copyright (and deserves the credit)?
Thiemo
> Signed-off-by: Riku Voipio <riku.voipio@iki.fi>
> ---
> linux-user/signal.c | 37 +++++++++++++++++++++++++------------
> 1 files changed, 25 insertions(+), 12 deletions(-)
>
> diff --git a/linux-user/signal.c b/linux-user/signal.c
> index e0f6aaf..dac9933 100644
> --- a/linux-user/signal.c
> +++ b/linux-user/signal.c
> @@ -24,6 +24,7 @@
> #include <unistd.h>
> #include <signal.h>
> #include <errno.h>
> +#include <assert.h>
> #include <sys/ucontext.h>
>
> #include "qemu.h"
> @@ -328,21 +329,33 @@ static inline void free_sigqueue(CPUState *env, struct sigqueue *q)
> static void __attribute((noreturn)) force_sig(int sig)
> {
> int host_sig;
> + struct sigaction act;
> host_sig = target_to_host_signal(sig);
> fprintf(stderr, "qemu: uncaught target signal %d (%s) - exiting\n",
> sig, strsignal(host_sig));
> -#if 1
> - _exit(-host_sig);
> -#else
> - {
> - struct sigaction act;
> - sigemptyset(&act.sa_mask);
> - act.sa_flags = SA_SIGINFO;
> - act.sa_sigaction = SIG_DFL;
> - sigaction(SIGABRT, &act, NULL);
> - abort();
> - }
> -#endif
> +
> + /* The proper exit code for dieing from an uncaught signal is
> + * -<signal>. The kernel doesn't allow exit() or _exit() to pass
> + * a negative value. To get the proper exit code we need to
> + * actually die from an uncaught signal. Here the default signal
> + * handler is installed, we send ourself a signal and we wait for
> + * it to arrive. */
> + sigfillset(&act.sa_mask);
> + act.sa_handler = SIG_DFL;
> + sigaction(host_sig, &act, NULL);
> +
> + /* For some reason raise(host_sig) doesn't send the signal when
> + * statically linked on x86-64. */
> + kill(getpid(), host_sig);
> +
> + /* Make sure the signal isn't masked (just reuse the mask inside
> + of act) */
> + sigdelset(&act.sa_mask, host_sig);
> + sigsuspend(&act.sa_mask);
> +
> + /* unreachable */
> + assert(0);
> +
> }
>
> /* queue a signal so that it will be send to the virtual CPU as soon
> --
> 1.5.6.5
>
>
> --
> "rm -rf" only sounds scary if you don't have backups
>
next prev parent reply other threads:[~2008-11-27 11:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-23 21:37 [Qemu-devel] [PATCH] linux-user: Proper exit code for uncaught signals Riku Voipio
2008-11-27 11:42 ` Thiemo Seufer [this message]
2008-11-27 12:16 ` Jamie Lokier
2008-11-27 12:44 ` Riku Voipio
2008-11-27 12:21 ` Riku Voipio
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=20081127114233.GC15592@networkno.de \
--to=ths@networkno.de \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@iki.fi \
/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).