From: Sasha Levin <sashal@kernel.org>
To: "Barry K. Nathan" <barryn@pobox.com>
Cc: Mike Rapoport <rppt@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: Sun, 15 Nov 2026 19:55:48 -0500 [thread overview]
Message-ID: <avpUlHHaimEE_Rib@laps> (raw)
In-Reply-To: <2e149d01-c932-42d3-9698-c1555e542cb1@pobox.com>
On Sun, Nov 15, 2026 at 03:16:20PM -0800, Barry K. Nathan wrote:
>On 11/14/26 9:42 AM, Sasha Levin wrote:
>>On 2026-11-13, Salvatore Bonaccorso<carnil@debian.org> wrote:
>>>One followup to this. Reverting
>>>
>>>Fixes: 091c44b2d3c3 ("x86/mm/pat: Use pr_warn() for early W^X warnings")
>>>Fixes: 11d1ba991c07 ("x86/mm/pat: Fix effective RW computation in lookup_address_in_pgd_attr()")
>>Thanks for testing. Queued reverts of both for 6.12.
>
>I see that in the current stable-queue (commit
>3b8ff7f280433e6fb085dbc4f44ac6a138f352a0, "Fixes for all trees"),
>these two reverts are queued in staging-6.12, not queue-6.12, so
>queued up for 6.12.119 not 6.12.118 as far as I can tell.
>
>I don't know if this was some kind of oversight or if it's
>intentional, so I just wanted to bring it to your attention.
It's intentional. I don't want to play with the queue right before the release,
and we've already shipped this regression so there's no reason to rush.
--
Thanks,
Sasha
next prev parent reply other threads:[~2026-11-16 0:55 UTC|newest]
Thread overview: 7+ 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 [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=avpUlHHaimEE_Rib@laps \
--to=sashal@kernel.org \
--cc=barryn@pobox.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=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®