linux-kernel - Re: [PATCH v2 0/9] x86/xsaves: Fix XSAVES known issues

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:	Thu, 25 Feb 2016 13:07:15 -0800
From:	Yu-cheng Yu <yu-cheng.yu@...el.com>
To:	Dave Hansen <dave.hansen@...ux.intel.com>
Cc:	x86@...nel.org, "H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>, linux-kernel@...r.kernel.org,
	Andy Lutomirski <luto@...nel.org>,
	Borislav Petkov <bp@...e.de>,
	Sai Praneeth Prakhya <sai.praneeth.prakhya@...el.com>,
	"Ravi V. Shankar" <ravi.v.shankar@...el.com>,
	Fenghua Yu <fenghua.yu@...el.com>
Subject: Re: [PATCH v2 0/9] x86/xsaves: Fix XSAVES known issues

On Thu, Feb 25, 2016 at 12:57:28PM -0800, Dave Hansen wrote:
> On 02/25/2016 12:26 PM, Yu-cheng Yu wrote:
> > Patch 9 re-enables XSAVES.
> 
> Could we also add one more thing to this: A big, fat warning that
> supervisor states are not supported?  We might get that from an eventual
> use of xfeature_uncompacted_offset(), but we need something that's very
> clear.
> 
> I just don't want somebody coming along and shoving a supervisor state
> in to XCR0 and expecting it to work just because we have XSAVES support
> itself.  That might happen in-tree or out-of-tree as things get prototyped.

I will do that.

Yu-cheng