From: "Edgecombe, Rick P" <rick.p.edgecombe@intel.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-tip-commits@vger.kernel.org"
<linux-tip-commits@vger.kernel.org>
Cc: "tglx@linutronix.de" <tglx@linutronix.de>,
"Mehta, Sohil" <sohil.mehta@intel.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"Wang, Lei4" <lei4.wang@intel.com>,
"Pan, Lijun" <lijun.pan@intel.com>,
"x86@kernel.org" <x86@kernel.org>
Subject: Re: [tip: x86/urgent] x86/fpu: Invalidate FPU state correctly on exec()
Date: Thu, 24 Aug 2023 15:22:26 +0000 [thread overview]
Message-ID: <f2fdba6ecda7a6b1e2ea048a3863fb302cc0f8d1.camel@intel.com> (raw)
In-Reply-To: <169286827548.27769.3257744272966160176.tip-bot2@tip-bot2>
On Thu, 2023-08-24 at 09:11 +0000, tip-bot2 for Rick Edgecombe wrote:
> Fixes: 33344368cb08 ("x86/fpu: Clean up the fpu__clear() variants")
Oops, yes this looks correct. Sorry for the wrong characterization of
it being older.
prev parent reply other threads:[~2023-08-24 15:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 17:03 [PATCH] x86: Use __fpu_invalidate_fpregs_state() in exec Rick Edgecombe
2023-08-18 19:35 ` Lijun Pan
2023-08-18 21:56 ` Sohil Mehta
2023-08-24 0:04 ` Lijun Pan
2023-08-18 23:35 ` Sohil Mehta
2023-08-22 20:10 ` Sohil Mehta
2023-08-24 9:11 ` [tip: x86/urgent] x86/fpu: Invalidate FPU state correctly on exec() tip-bot2 for Rick Edgecombe
2023-08-24 15:22 ` Edgecombe, Rick P [this message]
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=f2fdba6ecda7a6b1e2ea048a3863fb302cc0f8d1.camel@intel.com \
--to=rick.p.edgecombe@intel.com \
--cc=lei4.wang@intel.com \
--cc=lijun.pan@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=sohil.mehta@intel.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--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