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  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:	Thu, 24 Jul 2014 01:10:32 +0200
From:	Andi Kleen <>
To:	Andy Lutomirski <>
Cc:	Andi Kleen <>,
	"H. Peter Anvin" <>,
	Borislav Petkov <>,
	"" <>,
	Linus Torvalds <>,
	X86 ML <>
Subject: Re: STI architectural question (and lretq -- I'm not even kidding)

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

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists