linux-kernel - Re: [RFC] 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]

Message-ID: <20110513160029.GD31888@redhat.com>
Date:	Fri, 13 May 2011 12:00:29 -0400
From:	Don Zickus <dzickus@...hat.com>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	huang ying <huang.ying.caritas@...il.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

On Fri, May 13, 2011 at 05:20:33PM +0200, Ingo Molnar wrote:
> 
> * 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.

Interesting.  Question though, what do you mean by 'event filtering'.  Is
that different then setting 'unknown_nmi_panic' panic on the commandline
or procfs?

Or are you suggesting something like registering another callback on the
die_chain that looks for DIE_NMIUNKNOWN as the event, swallows them and
implements the policy?  That way only on HEST related platforms would
register them while others would keep the default of 'Dazed and confused'
messages?

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/