| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20110513152033.GB3854@elte.hu> Date: Fri, 13 May 2011 17:20:33 +0200 From: Ingo Molnar <mingo@...e.hu> To: huang ying <huang.ying.caritas@...il.com> Cc: Don Zickus <dzickus@...hat.com>, Huang Ying <ying.huang@...el.com>, linux-kernel@...r.kernel.org, Andi Kleen <andi@...stfloor.org>, Robert Richter <robert.richter@....com>, Andi Kleen <ak@...ux.intel.com>, Borislav Petkov <bp@...en8.de> Subject: Re: [RFC] x86, NMI, Treat unknown NMI as hardware error * huang ying <huang.ying.caritas@...il.com> wrote: > > What should be done instead is to add an event for unknown NMIs, which can > > then be processed by the RAS daemon to implement policy. > > > > By using 'active' event filters it could even be set on a system to panic > > the box by default. > > If there is real fatal hardware error, maybe we have no luxury to go from NMI > handler to user space RAS daemon to determine what to do. System may explode, > bad data may go to disk before that. That is why i suggested: > > By using 'active' event filters it could even be set on a system to panic > > the box by default. event filters are evaluated in the kernel, so the panic could be instantaneous, without the event having to reach user-space. Thanks, Ingo -- 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