From: Dave Hansen <dave.hansen@intel.com>
To: Brian Geffon <bgeffon@google.com>, Guenter Roeck <groeck@google.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Willis Kung <williskung@google.com>, Borislav Petkov <bp@suse.de>,
Andy Lutomirski <luto@kernel.org>,
"# v4 . 10+" <stable@vger.kernel.org>,
the arch/x86 maintainers <x86@kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86/fpu: Correct pkru/xstate inconsistency
Date: Tue, 15 Feb 2022 09:10:01 -0800 [thread overview]
Message-ID: <792d3b0c-0cb8-a407-2618-a53f40e501ca@intel.com> (raw)
In-Reply-To: <CADyq12x0CXu_0Cs4At8GVqxWW6tvDGKzhESQpvL8cztHLnBG2w@mail.gmail.com>
On 2/15/22 08:19, Brian Geffon wrote:
> This only applies before 5.13, so 5.10.y and 5.4.y, the behavior
> decoupled PKRU from xstate in a long series from Thomas Gleixner, but
> the first commit where this would have been fixed in 5.13 would be:
>
> commit 954436989cc550dd91aab98363240c9c0a4b7e23
> Author: Thomas Gleixner <tglx@linutronix.de>
> Date: Wed Jun 23 14:02:21 2021 +0200
>
> x86/fpu: Remove PKRU handling from switch_fpu_finish()
Could you also describe why the >=5.13 fix for this isn't suitable for
older kernels?
next prev parent reply other threads:[~2022-02-15 17:12 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 15:36 [PATCH] x86/fpu: Correct pkru/xstate inconsistency Brian Geffon
2022-02-15 15:57 ` Guenter Roeck
2022-02-15 16:19 ` Brian Geffon
2022-02-15 17:02 ` Guenter Roeck
2022-02-15 17:10 ` Dave Hansen [this message]
2022-02-15 16:20 ` Greg KH
2022-02-15 17:07 ` Dave Hansen
2022-02-15 17:50 ` Brian Geffon
2022-02-15 17:55 ` Dave Hansen
2022-02-15 19:22 ` [PATCH stable 5.4,5.10] " Brian Geffon
2022-02-15 19:44 ` Greg KH
2022-02-15 21:32 ` Brian Geffon
2022-02-15 21:42 ` Dave Hansen
2022-02-15 21:48 ` Brian Geffon
2022-02-16 2:01 ` Brian Geffon
2022-02-16 10:05 ` Greg KH
2022-02-16 10:05 ` Greg KH
2022-02-16 15:14 ` Brian Geffon
2022-02-16 15:16 ` Dave Hansen
2022-02-17 13:31 ` Brian Geffon
2022-02-17 16:44 ` Dave Hansen
2022-02-17 20:42 ` Brian Geffon
2022-02-24 15:16 ` Dave Hansen
2022-02-25 12:01 ` Greg KH
2022-02-15 21:14 ` [PATCH] " Guenter Roeck
2022-02-15 21:36 ` Brian Geffon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=792d3b0c-0cb8-a407-2618-a53f40e501ca@intel.com \
--to=dave.hansen@intel.com \
--cc=bgeffon@google.com \
--cc=bp@suse.de \
--cc=groeck@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=williskung@google.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).