[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <45E09989.5070604@google.com>
Date: Sat, 24 Feb 2007 12:01:13 -0800
From: Markus Gutschke <markus@...gle.com>
To: David Howells <dhowells@...hat.com>
CC: "Kawai, Hidehiro" <hidehiro.kawai.ez@...achi.com>,
Andrew Morton <akpm@...l.org>,
kernel list <linux-kernel@...r.kernel.org>,
Pavel Machek <pavel@....cz>, Robin Holt <holt@....com>,
Alan Cox <alan@...rguk.ukuu.org.uk>,
Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>,
sugita <yumiko.sugita.yf@...achi.com>,
Satoshi OSHIMA <soshima@...hat.com>
Subject: Re: [PATCH 0/4] coredump: core dump masking support v3
David Howells wrote:
> How does it work when you can't actually get back to userspace to have
> userspace do the coredump? You still have to handle the userspace equivalents
> of double/triple faults.
My experience shows that there are only very rare occurrences of
situations where you cannot get back into userspace to do the coredump,
and the coredumper tries very hard never to cause additional faults.
While I am sure you could construct scenarios where this would happen,
realistically the only one I have run into were stack overflows, and
they can be handled by carefully setting up an alternate stack for
signal handlers -- just make sure the entire stack is already dirtied
before you run out of memory (or, turn of overcommitting).
Markus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists