From: Andrew Morton <akpm@linux-foundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-mm@kvack.org, mm-commits@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [GIT PULL] hotfixes for 6.19-rc7
Date: Tue, 20 Jan 2026 13:11:26 -0800 [thread overview]
Message-ID: <20260120131126.fcd6df1111d067948a8244c4@linux-foundation.org> (raw)
Linus, please merge this batch of hotfixes, thanks.
The following changes since commit 24d479d26b25bce5faea3ddd9fa8f3a6c3129ea7:
Linux 6.19-rc6 (2026-01-18 15:42:45 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm tags/mm-hotfixes-stable-2026-01-20-13-09
for you to fetch changes up to 16aca2c98a6fdf071e5a1a765a295995d7c7e346:
mm: restore per-memcg proactive reclaim with !CONFIG_NUMA (2026-01-20 09:34:27 -0800)
----------------------------------------------------------------
17 hotfixes. 12 are cc:stable, 16 are for MM.
- A 4 patch series from David Hildenbrand which fixes a few things
realted to hugetlb PMD sharing
- The remainder are singletons, please see their changelogs for details.
----------------------------------------------------------------
Andrew Cooper (1):
x86/kfence: avoid writing L1TF-vulnerable PTEs
Breno Leitao (1):
mm/kfence: fix potential deadlock in reboot notifier
David Hildenbrand (Red Hat) (4):
mm/hugetlb: fix hugetlb_pmd_shared()
mm/hugetlb: fix two comments related to huge_pmd_unshare()
mm/rmap: fix two comments related to huge_pmd_unshare()
mm/hugetlb: fix excessive IPI broadcasts when unsharing PMD tables using mmu_gather
Gal Pressman (1):
panic: only warn about deprecated panic_print on write access
Joanne Koong (1):
fs/writeback: skip AS_NO_DATA_INTEGRITY mappings in wait_sb_inodes()
Lorenzo Stoakes (3):
mm/vma: do not leak memory when .mmap_prepare swaps the file
mm: remove unnecessary and incorrect mmap lock assert
mm: do not copy page tables unnecessarily for VM_UFFD_WP
Mathieu Desnoyers (3):
mm: add missing static initializer for init_mm::mm_cid.lock
mm: rename cpu_bitmap field to flexible_array
mm: take into account mm_cid size for mm_struct static definitions
Matthew Wilcox (Oracle) (1):
migrate: correct lock ordering for hugetlb file folios
Suren Baghdasaryan (1):
Docs/mm/allocation-profiling: describe sysctrl limitations in debug mode
Yosry Ahmed (1):
mm: restore per-memcg proactive reclaim with !CONFIG_NUMA
Documentation/admin-guide/sysctl/vm.rst | 4 +
Documentation/mm/allocation-profiling.rst | 10 +++
arch/x86/include/asm/kfence.h | 29 +++++--
drivers/firmware/efi/efi.c | 2 +-
fs/fs-writeback.c | 7 +-
fs/fuse/file.c | 4 +-
include/asm-generic/tlb.h | 77 +++++++++++++++++-
include/linux/hugetlb.h | 17 ++--
include/linux/mm.h | 6 +-
include/linux/mm_types.h | 19 +++--
include/linux/pagemap.h | 11 +++
kernel/panic.c | 4 +-
mm/hugetlb.c | 131 ++++++++++++++++--------------
mm/init-mm.c | 5 +-
mm/internal.h | 8 --
mm/kfence/core.c | 17 ++--
mm/memory.c | 11 ++-
mm/migrate.c | 12 +--
mm/mmu_gather.c | 33 ++++++++
mm/rmap.c | 45 +++++-----
mm/vma.c | 11 ++-
mm/vmscan.c | 13 ++-
22 files changed, 341 insertions(+), 135 deletions(-)
next reply other threads:[~2026-01-20 21:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 21:11 Andrew Morton [this message]
2026-01-20 23:23 ` 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=20260120131126.fcd6df1111d067948a8244c4@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mm-commits@vger.kernel.org \
--cc=torvalds@linux-foundation.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