From: Dave Hansen <dave.hansen@intel.com>
To: Rik van Riel <riel@surriel.com>, linux-kernel@vger.kernel.org
Cc: kernel-team@meta.com, dave.hansen@linux.intel.com,
luto@kernel.org, peterz@infradead.org, bp@alien8.de,
x86@kernel.org, yu-cheng.yu@intel.com,
Rik van Riel <riel@meta.com>,
stable@kernel.org
Subject: Re: [PATCH 1/3] x86/mm: Fix potential overflow in user_pcid_flush_mask
Date: Tue, 3 Jun 2025 14:33:46 -0700 [thread overview]
Message-ID: <944968c1-a2a3-430a-bc9a-51ac431a0835@intel.com> (raw)
In-Reply-To: <5987ac95e4011c2b71d1c3cce13872571cff3ac7.camel@surriel.com>
On 6/3/25 14:20, Rik van Riel wrote:
>> Honestly, I'd just leave this out for the bug fix. If someone really
>> cares, we can come back and fix it up in mainline.
> I added the #ifdef at Ingo's request.
>
> I am happy to do the code in any way you two can
> agree on, but we should probably avoid the back
> and forth over many versions thing 🙂
Ingo, I don't think the #ifdef is worth it, especially for what needs to
go to stable@. The PTI config option is enabled quite widely, so it's
not doing much practically. If you feel strongly that it's required for
this series, then it needs to be broken out as a prerequisite and not
intermingled with the actual bug fix.
next prev parent reply other threads:[~2025-06-03 21:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-02 13:30 [PATCH 0/3] TLB flush fixes Rik van Riel
2025-06-02 13:30 ` [PATCH 1/3] x86/mm: Fix potential overflow in user_pcid_flush_mask Rik van Riel
2025-06-02 16:55 ` Dave Hansen
2025-06-03 21:20 ` Rik van Riel
2025-06-03 21:33 ` Dave Hansen [this message]
2025-06-02 13:30 ` [PATCH 2/3] x86/mm: Fix early boot use of INVPLGB Rik van Riel
2025-06-02 17:21 ` Dave Hansen
2025-06-02 13:30 ` [PATCH 3/3] x86/mm: Change cpa_flush() to call flush_kernel_range() directly Rik van Riel
2025-06-02 17:22 ` Dave Hansen
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=944968c1-a2a3-430a-bc9a-51ac431a0835@intel.com \
--to=dave.hansen@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=peterz@infradead.org \
--cc=riel@meta.com \
--cc=riel@surriel.com \
--cc=stable@kernel.org \
--cc=x86@kernel.org \
--cc=yu-cheng.yu@intel.com \
/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