From: Roland McGrath <roland@redhat.com>
To: phil-list@redhat.com
Cc: Axel <Axel.Zeuner@gmx.de>,
Linus Torvalds <torvalds@transmeta.com>,
<linux-kernel@vger.kernel.org>,
Ulrich Drepper <drepper@redhat.com>
Subject: Re: 2.5.39: Signal delivery to thread groups: Bug or feature
Date: Sun, 29 Sep 2002 03:47:37 -0700 [thread overview]
Message-ID: <200209291047.g8TAlbp03653@magilla.sf.frob.com> (raw)
In-Reply-To: Ingo Molnar's message of Sunday, 29 September 2002 12:27:11 +0200 <Pine.LNX.4.44.0209291222500.18396-100000@localhost.localdomain>
> we still have one more problem left in the signal handling area: atomicity
> of signal delivery. Eg. right now it's possible to have a signal 'in
> flight' for one specific thread, which manages to block it before handling
> the signal. What should the behavior be in that case? Does POSIX say
> anything about this?
Assuming you are talking about a process-global signal (not pthread_kill),
then POSIX does not permit this race condition. If there is any thread
that can take the signal (i.e. not blocking it, or is sigwait'ing for it),
then one such thread must take the signal. The selection of the thread and
it beginning its action (i.e. choosing a signal handler, and saving the
signal mask the signal handler will restore on its return; or process death)
must be atomic with respect to that thread blocking the signal.
next prev parent reply other threads:[~2002-09-29 10:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200209281638.g8SGcQi23877@mx1.redhat.com>
2002-09-29 8:25 ` Ingo Molnar
2002-09-29 16:56 ` Axel
2002-09-29 10:27 ` Ingo Molnar
2002-09-29 10:47 ` Roland McGrath [this message]
2002-09-29 12:47 ` [patch] atomic-thread-signals-2.5.39-B5 Ingo Molnar
2002-09-28 17:15 2.5.39: Signal delivery to thread groups: Bug or feature Axel
-- strict thread matches above, loose matches on Subject: below --
2002-09-28 17:14 Axel
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=200209291047.g8TAlbp03653@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=Axel.Zeuner@gmx.de \
--cc=drepper@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=phil-list@redhat.com \
--cc=torvalds@transmeta.com \
/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
all inboxes | Powered by JetHome®