mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Jesper Juhl <jesper.juhl@gmail.com>,
	Robert Wilkens <robw@optonline.net>,
	Bodo Stroesser <bstroesser@fujitsu-siemens.com>,
	Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>,
	Jan Engelhardt <jengelh@linux01.gwdg.de>,
	Chris Wright <chrisw@osdl.org>
Subject: Re: test_signal results AIX DU4 IRIX6 (was: [PATCH] Fix PPC signal handling of NODEFER, should not affect sa_mask)
Date: Fri, 12 Aug 2005 17:23:33 -0400	[thread overview]
Message-ID: <1123881813.5296.19.camel@localhost.localdomain> (raw)
In-Reply-To: <200508121316.55757.merritt@u.washington.edu>

I received this from someone. I'm BCCing him since he didn't email to
the LKML himself (for some reason, maybe he doesn't want spam), I'll
protect his identity. If he wants to take credit, he should CC everyone.


On Fri, 2005-08-12 at 13:16 -0700, Someone wrote:
> DU4
> ===
> [3] uname -a
> OSF1 hostname V4.0 878 alpha
> [4] ./test_signal 
> sa_mask blocks other signals
> SA_NODEFER does not block other signals

> SA_NODEFER does not affect sa_mask

The above here is what the patch does, and NOT what Linux currently
does.

> SA_NODEFER and sa_mask blocks sig

Same goes for the above here.

> !SA_NODEFER blocks sig
> SA_NODEFER does not block sig
> sa_mask blocks sig
> 
> AIX
> ===
> [36] uname -a
> AIX hostname 2 5 000A1B9A4C00
> [37] ./test_signal 
> sa_mask blocks other signals
> SA_NODEFER does not block other signals

> SA_NODEFER does not affect sa_mask
> SA_NODEFER and sa_mask blocks sig

Strike two. looks good for the patch.

> !SA_NODEFER blocks sig
> SA_NODEFER does not block sig
> sa_mask blocks sig
> 
> Irix 6.5
> ========
> [9] uname -a
> IRIX hostname 6.5 07201607 IP22
> [10] ./test_signal 
> sa_mask blocks other signals
> SA_NODEFER does not block other signals

> SA_NODEFER does not affect sa_mask
> SA_NODEFER and sa_mask blocks sig

Strike three, your out!

> !SA_NODEFER blocks sig
> SA_NODEFER does not block sig
> sa_mask blocks sig
> 

So Linux is not compliant with other unices.  So I guess I'll get going
on sending in patches for each architecture.

Oh, just to show you what Linux shows without the patch:

$ uname -a
Linux bilbo 2.6.12 #2 SMP Wed Jul 20 20:07:59 EDT 2005 i686 GNU/Linux

$ ./test_signal
sa_mask blocks other other signals
SA_NODEFER does not block other signals
SA_NODEFER affects sa_mask
SA_NODEFER and sa_mask does not block sig
!SA_NODEFER blocks sig
SA_NODEFER does not block sig
sa_mask blocks sig


And with the patch:

$ uname -a
Linux goliath 2.6.13-rc3 #5 SMP Fri Aug 12 14:39:38 EDT 2005 i686
GNU/Linux

$ ./test_signal
sa_mask blocks other signals
SA_NODEFER does not block other signals
SA_NODEFER does not affect sa_mask
SA_NODEFER and sa_mask blocks sig
!SA_NODEFER blocks sig
SA_NODEFER does not block sig
sa_mask blocks sig


-- Steve



           reply	other threads:[~2005-08-12 21:23 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <200508121316.55757.merritt@u.washington.edu>]

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=1123881813.5296.19.camel@localhost.localdomain \
    --to=rostedt@goodmis.org \
    --cc=akpm@osdl.org \
    --cc=bstroesser@fujitsu-siemens.com \
    --cc=chrisw@osdl.org \
    --cc=jengelh@linux01.gwdg.de \
    --cc=jesper.juhl@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robw@optonline.net \
    --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

all inboxes | Powered by JetHome®