mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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/urgent for 7.4-rc4
Date: Sun, 13 Sep 2026 15:53:56 -0700	[thread overview]
Message-ID: <20260913225356.1033865-1-dave.hansen@linux.intel.com> (raw)

Hi Linus,

Please pull some x86/urgent changes for 7.4-rc4.

The MADV_FREE one is notable for silently losing user data and having
been around for a couple of years. The main explanation I'd have for
its longevity is that it requires a few different things to align at
the same time: MADV_FREE, THP and heavy reclaim.

There's also a good set of x86/mm fixes from Lorenzo and company.
They look somewhat theoretical at first but they have actually been
hampering folks' ability mm work in the area.
The following changes since commit d2929113b15bfc06793b852aeba3d2db6d79fcc9:

  x86/MCE/AMD: Fix inverted interrupt enablement during storm handling (2026-09-08 09:16:32 +0200)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/x86_urgent_for_7.3-rc4

for you to fetch changes up to 27600805e62f800bacf990354632eae4e487d34c:

  x86/amd_node: Fix PCI device reference counting in amd_smn_init() (2026-09-10 18:05:43 -0700)

----------------------------------------------------------------
 * Fix user-space data loss with MADV_FREE and THP
 * Fix set_memory oopses
 * Fix addition of large constants in mul_u64_add_u64_div_u64()
 * Fix FineIBT hash offset in cfi_get_func_hash()
 * Fix PCI device reference counting in amd_smn_init()

----------------------------------------------------------------
David Laight (1):
      x86/div64: Fix addition of large constants in mul_u64_add_u64_div_u64()

Lorenzo Stoakes (ARM) (3):
      x86/mm/pat: Acquire init_mm write lock on collapse to avoid UAF
      x86/mm/pat: Acquire init_mm read lock on attribute changes to avoid UAF
      x86/mm/pat: Allocate split page tables as kernel page tables

Pedro Falcato (1):
      x86/alternatives: Exclude text poking against change_page_attr()

Soheil Hassas Yeganeh (1):
      x86/cfi: Fix FineIBT hash offset in cfi_get_func_hash()

Vernon Yang (1):
      x86/mm: Fix user-space data loss with MADV_FREE and THP

Yazen Ghannam (1):
      x86/amd_node: Fix PCI device reference counting in amd_smn_init()

 arch/x86/include/asm/div64.h   |   2 +-
 arch/x86/include/asm/pgtable.h |   2 +-
 arch/x86/kernel/alternative.c  | 111 +++++++++++++++++++++++++++--------------
 arch/x86/kernel/amd_node.c     |   6 +--
 arch/x86/mm/pat/set_memory.c   |  53 +++++++++++++++-----
 include/linux/mmap_lock.h      |   2 +
 6 files changed, 121 insertions(+), 55 deletions(-)

             reply	other threads:[~2026-09-13 22:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-13 22:53 Dave Hansen [this message]
2026-09-13 23:10 ` Linus Torvalds
2026-09-13 23:23   ` Linus Torvalds
2026-09-14  0:18   ` Dave Hansen
2026-09-14  1:04     ` Linus Torvalds
2026-09-14  1:12       ` Dave Hansen
2026-09-14 10:12       ` Orson Peters
2026-09-14 16:36         ` Linus Torvalds
2026-09-14  1:09 ` pr-tracker-bot

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=20260913225356.1033865-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®