[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <m162k64c7w.fsf@fess.ebiederm.org>
Date: Mon, 03 Oct 2011 03:10:43 -0700
From: ebiederm@...ssion.com (Eric W. Biederman)
To: prasad@...ux.vnet.ibm.com
Cc: linux-kernel@...r.kernel.org, crash-utility@...hat.com,
kexec@...ts.infradead.org, Vivek Goyal <vgoyal@...hat.com>,
Andi Kleen <andi@...stfloor.org>,
"Luck\, Tony" <tony.luck@...el.com>, anderson@...hat.com,
tachibana@....nes.nec.co.jp, oomichi@....nes.nec.co.jp
Subject: Re: [Patch 1/4][kernel][slimdump] Add new elf-note of type NT_NOCOREDUMP to capture slimdump
"K.Prasad" <prasad@...ux.vnet.ibm.com> writes:
> There are certain types of crashes induced by faulty hardware in which
> capturing crashing kernel's memory (through kdump) makes no sense (or sometimes
> dangerous).
>
> A case in point, is unrecoverable memory errors (resulting in fatal machine
> check exceptions) in which reading from the faulty memory location from the
> kexec'ed kernel will cause double fault and system reset (leaving no
> information for the user).
It does make plenty of sense, and I capture the all of the time.
It totally doesn't make sense to do this in the kernel when we can
filter this from userspace just fine.
Nacked-by: "Eric W. Biederman" <ebiederm@...ssion.com>
I thought we already had this discussion. Why is this silliness coming
back?
I especially dislike the notion of hardcoding policy in the kernel like this.
Eric
--
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