linux-kernel - RE: [Patch V0] x86, mce: Don't clear global error reporting banks during cpu

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: <3908561D78D1C84285E8C5FCA982C28F32AF0527@ORSMSX114.amr.corp.intel.com>
Date:	Fri, 4 Sep 2015 16:38:10 +0000
From:	"Luck, Tony" <tony.luck@...el.com>
To:	Borislav Petkov <bp@...en8.de>, "Raj, Ashok" <ashok.raj@...el.com>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"Boris Petkov" <bp@...e.de>,
	"linux-edac@...r.kernel.org" <linux-edac@...r.kernel.org>,
	"Ayoun, Serge" <serge.ayoun@...el.com>
Subject: RE: [Patch V0] x86, mce: Don't clear global error reporting banks
 during cpu_offline

> What does that mean? What does SGX have to do with MCI_CTL registers?
> Explain that in the commit message so that !Intel people can understand.

I think the SGX folk are worried that it might be possible to compromise the
integrity of code running in SGX if an attacker has control of the host and can
inject errors which are ignored because of MCi_CTL settings. Hence they have
the h/w drop out of SGX if they see anyone tamper with MCi_CTL

-Tony