From: Steven Rostedt <rostedt@goodmis.org>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: Andi Kleen <ak@suse.de>, LKML <linux-kernel@vger.kernel.org>,
rmk@arm.linux.org.uk, gerg@uclinux.org, jdike@karaya.com,
sammy@sammy.net, lethal@linux-sh.org, wli@holomorphy.com,
davem@davemloft.net, matthew@wil.cx, geert@linux-m68k.org,
paulus@samba.org, davej@codemonkey.org.uk, tony.luck@intel.com,
dev-etrax@axis.com, rpurdie@rpsys.net, spyro@f2s.com,
Robert Wilkens <robw@optonline.net>,
Bodo Stroesser <bstroesser@fujitsu-siemens.com>,
Jan Engelhardt <jengelh@linux01.gwdg.de>,
Chris Wright <chrisw@osdl.org>, Andrew Morton <akpm@osdl.org>,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: [PATCH] Convert sigaction to act like other unices
Date: Tue, 16 Aug 2005 13:04:23 -0400 [thread overview]
Message-ID: <1124211863.5764.31.camel@localhost.localdomain> (raw)
In-Reply-To: <9a874849050814052035ad2838@mail.gmail.com>
On Sun, 2005-08-14 at 14:20 +0200, Jesper Juhl wrote:
> On 8/13/05, Andi Kleen <ak@suse.de> wrote:
> > On Sat, Aug 13, 2005 at 10:00:14AM -0400, Steven Rostedt wrote:
> > > On Sat, 2005-08-13 at 14:39 +0200, Andi Kleen wrote:
> > > > On Fri, Aug 12, 2005 at 10:40:02PM -0400, Steven Rostedt wroqte:
> > > > > Here's a patch that converts all architectures to behave like other unix
> > > > > boxes signal handling. It's funny that I didn't need to change the m68k
> > > > > architecture, since it was the only one that already behaves this way!
> > > > > (the m68knommu does not!)
> > > >
> [snip]
> >
> > My general feeling about the change is that it risks breaking programs
> > and doesn't seem to have any compelling advantages,
> > so unless there is a bug demonstrated I wouldn't apply it.
> >
> > -Andi
> >
>
> As I see it, the advantages are that we would a) match the
> documentation (man pages & posix/SUS) which makes things easier for
> application writers who won't have to scratch their beards wondering
> why Linux doesn't behave like the docs say. And b) Linux behaviour
> would match what most (all?) other Unices do, so there'll be less
> hassle/bugs when porting apps from other systems to Linux. To me,
> those look like significant bennefits.
> As for the "it may break programs" bit, that of course is a concern,
> but one way around that would be to stick it in -mm and let it cook
> for a few kernel releases. Say we stick it in -mm with a plan to merge
> it into 2.6.16-rc1, that should give it quite a bit of time to
> determine if it breaks apps (and if it does, to fix those apps).
Has there been a verdict on this. Are we going to
a) leave Linux "as-is" and be different than the man pages and POSIX as
well as pretty much every other Unix out there. But..., we keep from
breaking any linux-only applications out there that actually depend on
this behaviour (if there were any).
b) add the patch (in -mm or early 14 or later), see if any applications
break, but we will finally match the man pages and etc.
Just curious.
-- Steve
next prev parent reply other threads:[~2005-08-16 17:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-13 2:40 Steven Rostedt
2005-08-13 12:39 ` Andi Kleen
2005-08-13 14:00 ` Steven Rostedt
2005-08-13 21:29 ` Andi Kleen
2005-08-14 12:20 ` Jesper Juhl
2005-08-16 17:04 ` Steven Rostedt [this message]
2005-08-16 17:15 ` Linus Torvalds
2005-08-13 14:25 ` Steven Rostedt
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=1124211863.5764.31.camel@localhost.localdomain \
--to=rostedt@goodmis.org \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=bstroesser@fujitsu-siemens.com \
--cc=chrisw@osdl.org \
--cc=davej@codemonkey.org.uk \
--cc=davem@davemloft.net \
--cc=dev-etrax@axis.com \
--cc=geert@linux-m68k.org \
--cc=gerg@uclinux.org \
--cc=jdike@karaya.com \
--cc=jengelh@linux01.gwdg.de \
--cc=jesper.juhl@gmail.com \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=paulus@samba.org \
--cc=rmk@arm.linux.org.uk \
--cc=robw@optonline.net \
--cc=rpurdie@rpsys.net \
--cc=sammy@sammy.net \
--cc=spyro@f2s.com \
--cc=tony.luck@intel.com \
--cc=torvalds@osdl.org \
--cc=wli@holomorphy.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
Powered by JetHome