linux-kernel - Re: [PATCH Bugfix 1/4] x86/xsave.c: Fix xstate offsets and sizes enumeration

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

Date:	Tue, 21 Apr 2015 07:28:29 -0700
From:	Dave Hansen <dave.hansen@...el.com>
To:	Thomas Gleixner <tglx@...utronix.de>,
	Fenghua Yu <fenghua.yu@...el.com>
CC:	"H. Peter Anvin" <hpa@...ux.intel.com>,
	Ingo Molnar <mingo@...nel.org>,
	Asit K Mallick <asit.k.mallick@...el.com>,
	Glenn Williamson <glenn.p.williamson@...el.com>,
	linux-kernel <linux-kernel@...r.kernel.org>, x86 <x86@...nel.org>
Subject: Re: [PATCH Bugfix 1/4] x86/xsave.c: Fix xstate offsets and sizes
 enumeration

On 04/21/2015 02:16 AM, Thomas Gleixner wrote:
> On Sat, 18 Apr 2015, Fenghua Yu wrote:
>> From: Fenghua Yu <fenghua.yu@...el.com>
>> When enumerating xstate offsets and sizes from cpuid (eax=0x0d, ecx>=2),
>> it's possible that state m is not implemented while state n (n>m)
>> is implemented. So enumeration shouldn't stop at state m.
>>
>> There is no platform configured like above yet. But this could be a problem
>> in the future.
> 
> So this is for future hardware. Why are you claiming this is a BUGFIX?

That was probably phrased badly.  I don't know of any platforms out
there in the wild where this will be an issue.  So we don't expect this
to impact any end users.

But, I'm not an end user.  This bug is impacting me today.  I'd like to
see it fixed as widely as possible so that end users have little chance
of running in to it in the future.

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