linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bruce Perens <bruce@perens.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Ulrich Drepper <drepper@redhat.com>,
	Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Posix says "undefined". Re: Signal left blocked after signal handler.
Date: Wed, 26 Nov 2003 11:34:01 -0800	[thread overview]
Message-ID: <3FC50029.7030706@perens.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0311261108350.1524@home.osdl.org>

Linus,

Posix says the behavior is undefined. See 
http://www.opengroup.org/onlinepubs/007904975/functions/sigprocmask.html .
I think it makes sense to leave the 2.6 behavior as it is.

    Thanks

    Bruce

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).
>
>But if ElectricFence is the only thing that cares, I'd rather just EF
>added a SA_NODEFER..
>  
>



  reply	other threads:[~2003-11-26 19:34 UTC|newest]

Thread overview: 10+ 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               ` Bruce Perens [this message]
2003-11-26 19:52               ` Jamie Lokier
2003-11-27  9:20 ` Herbert Xu

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=3FC50029.7030706@perens.com \
    --to=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 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).