From: Borislav Petkov <bp@alien8.de>
To: Dave Hansen <dave.hansen@linux.intel.com>
Cc: "Janusz Krzysztofik" <janusz.krzysztofik@linux.intel.com>,
x86@kernel.org, "Thomas Gleixner" <tglx@linutronix.de>,
"Ingo Molnar" <mingo@redhat.com>,
"Juergen Gross" <jgross@suse.com>,
"Andi Shyti" <andi.shyti@linux.intel.com>,
"Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>,
"Edgecombe, Rick P" <rick.p.edgecombe@intel.com>,
linux-kernel@vger.kernel.org, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v3 RESEND] x86/mm: Fix PAT bit missing from page protection modify mask
Date: Mon, 10 Jul 2023 10:05:19 +0200 [thread overview]
Message-ID: <20230710080519.GAZKu7v2N/eK/jYXPL@fat_crate.local> (raw)
In-Reply-To: <20230710073613.8006-2-janusz.krzysztofik@linux.intel.com>
On Mon, Jul 10, 2023 at 09:36:14AM +0200, Janusz Krzysztofik wrote:
> Assume that adding _PAGE_PAT to _PAGE_CHG_MASK doesn't break pte_modify()
> and its users, and go for it. Also, add _PAGE_PAT_LARGE to
That's my only worry.
I'd suggest we queue this but not send it to Linus now. Instead, let it
cook in linux-next for the whole 6.5 release cycle so that it can get at
least *some* testing.
Because if we send it now and something else obscure breaks in a weird
way in his tree, then we'll have to scramble to fix that too and it'll
be one helluva mess.
Dave?
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2023-07-10 8:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-10 7:36 Janusz Krzysztofik
2023-07-10 8:05 ` Borislav Petkov [this message]
2023-07-17 9:42 ` Janusz Krzysztofik
2023-07-10 17:58 ` Edgecombe, Rick P
2023-07-17 9:45 ` Janusz Krzysztofik
2023-07-17 21:25 ` Edgecombe, Rick P
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=20230710080519.GAZKu7v2N/eK/jYXPL@fat_crate.local \
--to=bp@alien8.de \
--cc=andi.shyti@linux.intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=janusz.krzysztofik@linux.intel.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marmarek@invisiblethingslab.com \
--cc=mingo@redhat.com \
--cc=rick.p.edgecombe@intel.com \
--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
all inboxes | Powered by JetHome®