linux-kernel - Re: STI architectural question (and lretq -- I'm not even kidding)

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] [day] [month] [year] [list]

Date:	Thu, 24 Jul 2014 15:15:23 -0700
From:	"H. Peter Anvin" <hpa@...ux.intel.com>
To:	Andi Kleen <andi@...stfloor.org>,
	Andy Lutomirski <luto@...capital.net>
CC:	Borislav Petkov <bp@...en8.de>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	X86 ML <x86@...nel.org>
Subject: Re: STI architectural question (and lretq -- I'm not even kidding)

On 07/23/2014 04:10 PM, Andi Kleen wrote:
>> I think that, other than broadcast MCEs, #MC that hits in kernel mode
>> is non-recoverable, or at least can't safely be recovered.  (There's a
>> separate APIC interrupt for recoverable errors, I think, but that's a
>> much saner interface.)
> 
> There are multiple valid cases where #MC can return.
> 

Indeed, not just broadcast #MC.

	-hpa


--
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/