From: Jamie Lokier <jamie@shareable.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Bruce Perens <bruce@perens.com>,
Ulrich Drepper <drepper@redhat.com>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Never mind. Re: Signal left blocked after signal handler.
Date: Wed, 26 Nov 2003 19:52:45 +0000 [thread overview]
Message-ID: <20031126195245.GF14383@mail.shareable.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0311261108350.1524@home.osdl.org>
Linus Torvalds wrote:
> I personally think it is "good taste" to actually set the SA_NODEFER flag
> if you know you depend on the behaviour, but if there are lots of existing
> applications that actually depend on the "forced punch-through" behaviour,
> then I'll obviously have to change the 2.6.x behaviour (a stable
> user-level ABI is a lot more important than my personal preferences).
I also have a program which depends on the behaviour of nesting
SIGSEGVs, however luckily I already set the SA_NODEFER flag :)
-- Jamie
next prev parent reply other threads:[~2003-11-26 19:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-26 17:39 Signal left blocked after signal handler Bruce Perens
2003-11-26 17:55 ` Linus Torvalds
[not found] ` <3FC4ED5F.4090901@perens.com>
2003-11-26 18:21 ` Linus Torvalds
[not found] ` <3FC4EF24.9040307@perens.com>
2003-11-26 18:34 ` Linus Torvalds
[not found] ` <3FC4F248.8060307@perens.com>
2003-11-26 18:45 ` Never mind. " Linus Torvalds
2003-11-26 19:04 ` Bruce Perens
2003-11-26 19:14 ` Linus Torvalds
2003-11-26 19:34 ` Posix says "undefined". " Bruce Perens
2003-11-26 19:52 ` Jamie Lokier [this message]
2003-11-27 9:20 ` Herbert Xu
-- strict thread matches above, loose matches on Subject: below --
2003-11-26 21:53 Never mind. " Albert Cahalan
2003-11-27 9:11 ` Ingo Oeser
2003-11-27 15:45 ` Albert Cahalan
2003-11-27 17:26 ` Jörn Engel
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=20031126195245.GF14383@mail.shareable.org \
--to=jamie@shareable.org \
--cc=bruce@perens.com \
--cc=drepper@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.