From: Dave Hansen <dave.hansen@linux.intel.com>
To: torvalds@linux-foundation.org
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
Dave Hansen <dave.hansen@linux.intel.com>
Subject: [GIT PULL] x86/mm for 7.4-rc1
Date: Mon, 19 Oct 2026 08:45:29 -0700 [thread overview]
Message-ID: <20261019154529.1878897-1-dave.hansen@linux.intel.com> (raw)
Hi Linus,
Please pull some x86/mm changes for 7.4-rc1. The __add_pages() and
pgd_clear() ones are pretty mundane.
But the W^X ones are worth calling out. Effectively, the checks that
were supposed to be looking out for Write+Exec permission mappings
were busted. This fixes them, so we should all be on the lookout for
new warnings, both false positives and real ones.
--
The following changes since commit df2908090cda368b01ff43709f51890076c56157:
Linux 7.3-rc2 (2026-09-06 15:07:20 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/x86_mm_for_7.4-rc1
for you to fetch changes up to d92b5ac5aeba1ffc734576e30a5bca882722de76:
x86/mm: Fix spurious warning on __add_pages() failure (2026-10-01 05:04:44 -0700)
----------------------------------------------------------------
- Fix void/int conditional in pgd_clear()
- Fix spurious warning on __add_pages() failure
- Make W^X detection actually work
----------------------------------------------------------------
Jose A. Perez de Azpillaga (1):
x86/mm: Fix void/int conditional in pgd_clear()
Lance Yang (1):
x86/mm: Fix spurious warning on __add_pages() failure
Mike Rapoport (Microsoft) (2):
x86/mm/pat: Fix effective RW computation in lookup_address_in_pgd_attr()
x86/mm/pat: Use pr_warn() for early W^X warnings
arch/x86/include/asm/pgtable.h | 6 +++++-
arch/x86/mm/init_64.c | 3 ++-
arch/x86/mm/pat/set_memory.c | 23 +++++++++++++++++++----
3 files changed, 26 insertions(+), 6 deletions(-)
reply other threads:[~2026-10-19 15:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20261019154529.1878897-1-dave.hansen@linux.intel.com \
--to=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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®