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]
Date:	Thu, 07 Oct 2010 08:32:30 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Jan Beulich <JBeulich@...ell.com>
CC:	linux-kernel@...r.kernel.org
Subject: Re: patch disabling use of PSE on Atom CPUs with a certain	 erratum

On 10/07/2010 08:29 AM, Jan Beulich wrote:
>>
>> You're right... I misremembered.  The question is what to do at this
>> point, since we're already in trouble.  A possible failure on startup
>> seems better than a state in which we could get data corruption at
>> almost any time.
> 
> The only possible (afaict) way to address this would be to check for
> the erratum in the boot code, and establish 4k page mappings from
> the beginning. That's likely going to be ugly though.
> 

Well, I guess we could do on 64 bits what we do on 32 bits, and always
use 4K pages for the initial bootstrap, to then be coalesced if PSE is
supported.  Again, ugly.

> The main reason I was asking was not so much to trigger a code
> change, but to understand the implications (since both the comment
> in the code and the changeset comment don't really hint at this
> leaving a problem open for 64-bit), to some degree to understand
> whether e.g. Xen would also need such a workaround (if anyone
> cares to run Xen on Atoms).

Well, keep in mind that the right thing really is to get the microcode
update into the CPU early... i.e. in the BIOS, or in a pinch, from the
bootloader -- but before the kernel runs.

	-hpa

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ