linux-kernel - Re: [PATCH v8 3/6] x86/fpu: Initialize guest fpstate and FPU pseudo container from guest defaults

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: <aDjQu1cxLP9DiyuY@AUSJOHALLEN.amd.com>
Date: Thu, 29 May 2025 16:25:15 -0500
From: John Allen <john.allen@....com>
To: Chao Gao <chao.gao@...el.com>
Cc: x86@...nel.org, linux-kernel@...r.kernel.org, kvm@...r.kernel.org,
	tglx@...utronix.de, dave.hansen@...el.com, seanjc@...gle.com,
	pbonzini@...hat.com, peterz@...radead.org,
	rick.p.edgecombe@...el.com, weijiang.yang@...el.com, bp@...en8.de,
	chang.seok.bae@...el.com, xin3.li@...el.com,
	Ingo Molnar <mingo@...hat.com>,
	Dave Hansen <dave.hansen@...ux.intel.com>,
	"H. Peter Anvin" <hpa@...or.com>, Kees Cook <kees@...nel.org>,
	Stanislav Spassov <stanspas@...zon.de>,
	Oleg Nesterov <oleg@...hat.com>, Eric Biggers <ebiggers@...gle.com>
Subject: Re: [PATCH v8 3/6] x86/fpu: Initialize guest fpstate and FPU pseudo
 container from guest defaults

On Thu, May 22, 2025 at 08:10:06AM -0700, Chao Gao wrote:
> fpu_alloc_guest_fpstate() currently uses host defaults to initialize guest
> fpstate and pseudo containers. Guest defaults were introduced to
> differentiate the features and sizes of host and guest FPUs. Switch to
> using guest defaults instead.
> 
> Adjust __fpstate_reset() to handle different defaults for host and guest
> FPUs. And to distinguish between the types of FPUs, move the initialization
> of indicators (is_guest and is_valloc) before the reset.
> 
> Suggested-by: Chang S. Bae <chang.seok.bae@...el.com>
> Signed-off-by: Chao Gao <chao.gao@...el.com>
> Reviewed-by: Rick Edgecombe <rick.p.edgecombe@...el.com>

Reviewed-by: John Allen <john.allen@....com>