linux-kernel - Re: [Xen-devel] PROBLEM: kernel panic xsave

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]

Message-Id: <5626613002000078000ACE3B@prv-mh.provo.novell.com>
Date:	Tue, 20 Oct 2015 07:43:44 -0600
From:	"Jan Beulich" <JBeulich@...e.com>
To:	"John Doe" <securef33d@...il.com>,
	"Boris Ostrovsky" <boris.ostrovsky@...cle.com>
Cc:	"Ingo Molnar" <mingo@...nel.org>, <x86@...nel.org>,
	<xen-devel@...ts.xen.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [Xen-devel] PROBLEM: kernel panic xsave_init

>>> On 20.10.15 at 15:22, <boris.ostrovsky@...cle.com> wrote:
> The reason I think its this commit is that RAX, RDX and RCX look very 
> much like arguments to xsetbv (which xstate_enable_boot_cpu() executes) 
> and RAX value is 0x1f, which has two new bits that this commit defined.

That would be the two MPX related bits, yet us (luckily) white listing
leaf 7 in pv_cpuid(), it is quite easy to validate that we don't expose
this feature to PV(H) guests. Sadly the story is different for HVM
guests (where the leaf handling uses black listing), but the register
dump here clearly points to a PV guest (or Dom0).

Jan

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