From: Dave Hansen <dave.hansen@intel.com>
To: K MURALI Hitesh <hitesh.murali@thalesgroup.com>,
"hitesh.murali@imperva.com" <hitesh.murali@imperva.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Andy Lutomirski <luto@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Borislav Petkov <bp@alien8.de>, "x86@kernel.org" <x86@kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Rick Edgecombe <rick.p.edgecombe@intel.com>,
Yu-cheng Yu <yu-cheng.yu@intel.com>,
"Mike Rapoport (IBM)" <rppt@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86/mm/fault: Test _PAGE_RW, not pte_write(), in spurious_kernel_fault_check()
Date: Thu, 1 Oct 2026 13:37:27 -0700 [thread overview]
Message-ID: <86b5bb44-9f0b-4d75-991f-3ff510a220f6@intel.com> (raw)
In-Reply-To: <MR0P264MB69837D7B9DF99BBA6333DB60E68A2@MR0P264MB6983.FRAP264.PROD.OUTLOOK.COM>
On 10/1/26 13:29, K MURALI Hitesh wrote:
> THALES GROUP LIMITED DISTRIBUTION to email recipients
This mail is pretty badly malformed and won't make it to the mailing
list archives anyway.
I'll take your patch as a very good report of a theoretical issue and
squirrel it away to look at on some future rainy day that I have some
spare time. I'll credit you as the bug reporter if it ever gets fixed.
I'm not going to be able to take a patch from you to fix it today,
though. It's not a practical bug that needs fixing.
next prev parent reply other threads:[~2026-10-01 20:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 16:12 Hitesh Murali via B4 Relay
2026-10-01 16:24 ` Dave Hansen
[not found] ` <MR0P264MB69837D7B9DF99BBA6333DB60E68A2@MR0P264MB6983.FRAP264.PROD.OUTLOOK.COM>
2026-10-01 20:37 ` Dave Hansen [this message]
2026-10-01 16:34 ` 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=86b5bb44-9f0b-4d75-991f-3ff510a220f6@intel.com \
--to=dave.hansen@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hitesh.murali@imperva.com \
--cc=hitesh.murali@thalesgroup.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rick.p.edgecombe@intel.com \
--cc=rppt@kernel.org \
--cc=tglx@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
all inboxes | Powered by JetHome®