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]
Date:	Wed, 19 Dec 2012 15:57:24 -0800
From:	"H. Peter Anvin" <>
To:	Borislav Petkov <>, Jacob Shin <>,
	Yinghai Lu <>,
	"H. Peter Anvin" <>,
	"Yu, Fenghua" <>,
	"" <>,
	"" <>,
	"" <>,
	Konrad Rzeszutek Wilk <>,
	Stefano Stabellini <>
Subject: Re: [tip:x86/microcode] x86/microcode_intel_early.c: Early update
 ucode on Intel's CPU

On 12/19/2012 03:55 PM, Borislav Petkov wrote:
> On Wed, Dec 19, 2012 at 03:50:14PM -0800, H. Peter Anvin wrote:
>> We are trying to discuss mitigation strategies with you, but you
>> haven't really given us any useful information, e.g. what happens near
>> the various boundaries of the hole, what could trigger prefeching into
>> the range, and what it would take to fix the BIOSes.
> Another thing we could do (I admit it is ugly) is to add a quirk to the
> #MC handler and detect that specific condition by looking at the address
> reported in MCi_ADDR and exit early by not panicking the system.
> Again, this is ugly but a possibility, still.

I would really, really hate to have to deal with an early MCE handler, too.


H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.

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