From: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>
To: Mike Rapoport <rppt@kernel.org>
Cc: Sasha Levin <sashal@kernel.org>,
Nathan Chancellor <nathan@kernel.org>,
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, "H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
regressions@lists.linux.dev,
Salvatore Bonaccorso <carnil@debian.org>
Subject: Re: [REGRESSION 6.12.117] CPA detected W^X violation: 0000000000000121 -> 0000000000000123 range: 0xffffffffc0477000 - 0xffffffffc0477fff PFN 109c1f and WARNING at arch/x86/mm/pat/set_memory.c:665 __change_page_attr_set_clr+0xf62/0xfb0
Date: Mon, 16 Nov 2026 16:30:03 +0530 [thread overview]
Message-ID: <3477f124-bfdf-4dc2-b05b-5048eda97724@oracle.com> (raw)
In-Reply-To: <avrhRp9Je2ip6bKM@kernel.org>
Hi Mike,
On 16/11/26 4:26 pm, Mike Rapoport wrote:
>> Quick Note: We are just reverting the fixes just removed the fixes to the
>> checker and the actual broken commit is: commit: 88a817e60dbb ("x86/its: Use
>> dynamic thunks for indirect branches") that introduced this problem.
> It didn't introduce a real problem, the permission are correct in the end.
> It's just the intermediate state that causes warnings.
>
thanks a lot for correcting!
Regards,
Harshit
next prev parent reply other threads:[~2026-11-16 11:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 12:47 Salvatore Bonaccorso
2026-11-13 18:50 ` Salvatore Bonaccorso
2026-11-14 17:42 ` Sasha Levin
2026-11-15 23:16 ` Barry K. Nathan
2026-11-16 0:55 ` Sasha Levin
2026-11-16 9:31 ` Harshit Mogalapalli
2026-11-16 10:56 ` Mike Rapoport
2026-11-16 11:00 ` Harshit Mogalapalli [this message]
2026-11-15 6:21 ` Mike Rapoport
2026-11-15 14:47 ` Sasha Levin
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=3477f124-bfdf-4dc2-b05b-5048eda97724@oracle.com \
--to=harshit.m.mogalapalli@oracle.com \
--cc=bp@alien8.de \
--cc=carnil@debian.org \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=nathan@kernel.org \
--cc=peterz@infradead.org \
--cc=regressions@lists.linux.dev \
--cc=rppt@kernel.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tglx@kernel.org \
--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®