linux-kernel - Re: Hardware Error Kernel Mini-Summit

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: <20100524171330.GC7145@sgi.com>
Date:	Mon, 24 May 2010 12:13:30 -0500
From:	Russ Anderson <rja@....com>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Tony Luck <tony.luck@...el.com>, Joe Perches <joe@...ches.com>,
	Mauro Carvalho Chehab <mchehab@...hat.com>,
	Hidetoshi Seto <seto.hidetoshi@...fujitsu.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	"bluesmoke-devel@...ts.sourceforge.net" 
	<bluesmoke-devel@...ts.sourceforge.net>,
	Linux Edac Mailing List <linux-edac@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	Ben Woodard <woodard@...hat.com>,
	Matt Domsch <Matt_Domsch@...l.com>,
	Doug Thompson <dougthompson@...ssion.com>,
	Borislav Petkov <bp@...64.org>,
	"Young, Brent" <brent.young@...el.com>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Frédéric Weisbecker <fweisbec@...il.com>,
	Arnaldo Carvalho de Melo <acme@...hat.com>,
	Russ Anderson <rja@....com>
Subject: Re: Hardware Error Kernel Mini-Summit

On Wed, May 19, 2010 at 12:00:02AM +0200, Ingo Molnar wrote:
> * Tony Luck <tony.luck@...el.com> wrote:
> 
> > [...] Getting from a machine check handler through some 
> > context switches (and page faults etc.) to a user level 
> > daemon before the error gets recorded looks to be really 
> > hard.
> 
> As Boris mentioned it too, critical policy action can and 
> will be done straight in the kernel.

That is how it is done in ia64.  The MCA interrupt 
handler does the low level handling.  It makes sure
all the cpus have rendezvoused, looks at the MCA record
to determine what happend and does whatever recovery 
steps are needed, such as kill the application.

It definitely needs to be handled in the kernel.

> 	Ingo

-- 
Russ Anderson, OS RAS/Partitioning Project Lead  
SGI - Silicon Graphics Inc          rja@....com
--
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/