Messages in this thread | | | Date | Mon, 28 Jun 2004 23:49:42 +0200 | From | Jörn Engel <> | Subject | Re: [patch] signal handler defaulting fix ... |
| |
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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |