Messages in this thread | | | Date | Wed, 30 Mar 2011 19:51:06 +0200 | From | Borislav Petkov <> | Subject | Re: [PATCH RFC 2/2] events/hw_event: Create a Hardware Anomaly Report Mechanism (HARM) |
| |
On Wed, Mar 30, 2011 at 01:27:43PM -0400, Luck, Tony wrote: > > A INT13 persistent data saving will probably be too hard to implement for > > all kind of storages. So, it will probably need lots of hack in order to > > work. Also, some hardware may even not have any local hard disk. Not sure > > if it is worth to spend time on it. > > Linus was pretty clear that he didn't like the idea when > it came up a few weeks ago in the: > [PATCH 0/2][concept RFC] x86: BIOS-save kernel log to disk upon panic > thread. > > Linus ranted: > > Quite frankly, I'm not likely to _ever_ merge anything like this. > > > > Over the years, many people have tried to write things to disk on > > oops. I refuse to take it. No way in hell do I want the situation of > > "the system is screwed, so let's overwrite the disk" to be something > > the kernel I release might do. It's crazy. That disk is a lot more > > important than the kernel, and overwriting it when we might have > > serious memory corruption issues or something is not a thing I feel is > > appropriate. > > I agree with him - writing to disk from a known broken kernel (using > a probably buggy BIOS) is a disaster waiting to happen to somebody's > disk.
I can't say I don't agree. The reference to the BIOS method was simply to say that we need some kind of a solution for saving OOPSen and other error info on clients too, with no pers. storage hw. And frankly, and AFAICT, we don't have one that would work reliably on existing hw right now :(.
-- Regards/Gruss, Boris.
Advanced Micro Devices GmbH Einsteinring 24, 85609 Dornach General Managers: Alberto Bozzo, Andrew Bowd Registration: Dornach, Gemeinde Aschheim, Landkreis Muenchen Registergericht Muenchen, HRB Nr. 43632 -- 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/
| |