[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b3464e21-95e8-a80e-bf98-3c90c06afb91@intel.com>
Date: Fri, 5 Aug 2022 10:24:04 -0700
From: Dave Hansen <dave.hansen@...el.com>
To: Kyle Huey <me@...ehuey.com>,
Dave Hansen <dave.hansen@...ux.intel.com>,
Thomas Gleixner <tglx@...utronix.de>,
Borislav Petkov <bp@...en8.de>
Cc: Ingo Molnar <mingo@...hat.com>, x86@...nel.org,
"H. Peter Anvin" <hpa@...or.com>,
Paolo Bonzini <pbonzini@...hat.com>,
Andy Lutomirski <luto@...nel.org>,
Peter Zijlstra <peterz@...radead.org>,
linux-kernel@...r.kernel.org,
Robert O'Callahan <robert@...llahan.org>,
David Manouchehri <david.manouchehri@...eup.net>,
Borislav Petkov <bp@...e.de>, kvm@...r.kernel.org,
stable@...r.kernel.org
Subject: Re: [PATCH v2] x86/fpu: Allow PKRU to be (once again) written by
ptrace.
On 8/3/22 20:16, Kyle Huey wrote:
> When management of the PKRU register was moved away from XSTATE, emulation
> of PKRU's existence in XSTATE was added for APIs that read XSTATE, but not
> for APIs that write XSTATE. This can be seen by running gdb and executing
> `p $pkru`, `set $pkru = 42`, and `p $pkru`. On affected kernels (5.14+) the
> write to the PKRU register (which gdb performs through ptrace) is ignored.
Do you happen to have a reproducer for this sitting around? I'd love to
get an addition to the pkeys selftest/ in place to make sure we don't
break this again. PKRU is a very special snowflake.
Powered by blists - more mailing lists