linux-kernel - Re: [PATCH -v3 5/6] x86, NMI, treat unknown NMI as hardware error

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 11 Oct 2010 17:08:29 -0400
From:	Don Zickus <dzickus@...hat.com>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Huang Ying <ying.huang@...el.com>, Ingo Molnar <mingo@...e.hu>,
	"H. Peter Anvin" <hpa@...or.com>, linux-kernel@...r.kernel.org,
	Robert Richter <robert.richter@....com>
Subject: Re: [PATCH -v3 5/6] x86, NMI, treat unknown NMI as hardware error

On Sun, Oct 10, 2010 at 04:13:11PM +0200, Andi Kleen wrote:
> > > These systems are identified via the presentation of APEI HEST or
> > > some PCI ID of the host bridge. The PCI ID of host bridge instead of
> > > DMI ID is used, so that the checking can be done based on the platform
> > > type instead of motherboard. This should be simpler and sufficient.
> > > 
> > > The method to identify the platforms is designed by Andi Kleen.
> > 
> > Why not make the new flag also a boot option so you can force it on for
> > platforms where we don't auto whitelist it.
> 
> You can already set it at run time using sysctl.
> 
> echo 1 > /proc/sys/kernel/panic_on_unrecovered_nmi
> echo 1 > /proc/sys/kernel/panic_on_io_nmi

I get the impression Alan was talking about the option

unknown_nmi_as_hwerr

which isn't hooked into a sysctl but will cause machines to panic.

Cheers,
Don
--
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/