From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Andrew Morton <akpm@osdl.org>
Cc: Davide Libenzi <davidel@xmailserver.org>,
linux-kernel@vger.kernel.org, torvalds@osdl.org
Subject: Re: [patch] signal handler defaulting fix ...
Date: Mon, 28 Jun 2004 23:49:42 +0200 [thread overview]
Message-ID: <20040628214942.GC29901@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <20040628144003.40c151ff.akpm@osdl.org>
On Mon, 28 June 2004 14:40:03 -0700, Andrew Morton wrote:
> Davide Libenzi <davidel@xmailserver.org> wrote:
> >
> >
> > Following up from the other thread (2.6.x signal handler bug) this bring
> > 2.4 behaviour in 2.6.
> >
>
> Pity the poor person who tries to understand this change in a year's time.
> Could we have a real changelog please?
It better be a good one. I've hit a real problem that raised more
than a few eyebrows. In short, if some program is stupid enough to
cause a segfault inside a segfault-handler, it doesn't have a reason
to survive.
Your patch will let the poor creature live an unhappy life. No good.
Jörn
--
More computing sins are committed in the name of efficiency (without
necessarily achieving it) than for any other single reason - including
blind stupidity.
-- W. A. Wulf
next prev parent reply other threads:[~2004-06-28 21:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-28 21:34 [patch] signal handler defaulting fix Davide Libenzi
2004-06-28 21:40 ` Andrew Morton
2004-06-28 21:49 ` Linus Torvalds
2004-06-28 21:55 ` Davide Libenzi
2004-06-28 22:08 ` Linus Torvalds
2004-06-28 22:13 ` Davide Libenzi
2004-06-29 1:24 ` Edgar Toernig
2004-06-29 12:02 ` Jörn Engel
2004-06-28 21:49 ` Jörn Engel [this message]
[not found] <2cfBL-6uJ-9@gated-at.bofh.it>
2004-07-03 13:54 ` Kai Henningsen
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=20040628214942.GC29901@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=akpm@osdl.org \
--cc=davidel@xmailserver.org \
--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.