linux-kernel - Re: [GIT PULL] x86 fixes

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4B522B23.5090903@zytor.com>
Date:	Sat, 16 Jan 2010 13:09:55 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
CC:	Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org,
	Thomas Gleixner <tglx@...utronix.de>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [GIT PULL] x86 fixes

On 01/16/2010 01:06 PM, H. Peter Anvin wrote:
> On 01/16/2010 12:34 PM, Linus Torvalds wrote:
>>
>>
>> On Sat, 16 Jan 2010, Ingo Molnar wrote:
>>>
>>> Cyrill Gorcunov (1):
>>>       x86: kernel_thread() -- initialize SS to a known state
>>
>> This looks bogus. Why does it do it only on x86-64?
>>
>> Either people care about SS or they don't (the answer, I suspect, is "they 
>> don't"). But if they care, we should do it on both 32-bit _and_ 64-bit, 
>> no?
>>
> 
> It is bogus -- it's basically Xen braindamage.
> 

As to why make it x86-64 only... it matches what the old assembly code
did.  We figured that that was the lowest risk option for unbreaking Xen.

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