public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Chris Friesen" <cfriesen@nortel.com>
To: linux-kernel@vger.kernel.org
Subject: simultaneous signal handling and setjmp/longjmp
Date: Fri, 06 Nov 2009 17:09:50 -0600	[thread overview]
Message-ID: <4AF4ACBE.5030005@nortel.com> (raw)

I've got a bit of an odd hypothetical question dealing with signals and
setjmp/longjmp.

Suppose we have an app with multiple signals pending.  (Say, SIGALRM and
SIGSEGV.)  In the signal handler for SIGSEGV, we're going to call call
longjmp().  (Yes, I'm aware of the issues.)

At this point we're still in the kernel and both SIGSEGV and SIGALARM
are pending. What happens?

If we run the SIGSEGV handler does the SIGALARM stay pending until the
segfault handler completes?  What happens when the segfault handler
calls longjmp()?  Does the SIGALARM handler get called on the logical
return from sigsetjmp(), and if so how does that happen since the glibc
code for setjmp/longjmp doesn't seem to call any kernel syscalls?

Thanks for any information you can provide...

Chris

                 reply	other threads:[~2009-11-06 23:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4AF4ACBE.5030005@nortel.com \
    --to=cfriesen@nortel.com \
    --cc=linux-kernel@vger.kernel.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