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 7.2-rc5
Date: Mon, 20 Jul 2026 11:39:47 -0700 [thread overview]
Message-ID: <20260720113947.6b43f86cede7f20c4126650b@linux-foundation.org> (raw)
Linus, please merge this batch of hotfixes, thanks.
The following changes since commit 0e35b9b6ec0ffcc5e23cbdec09f5c622ad532b53:
Merge tag 'mm-hotfixes-stable-2026-07-06-17-49' of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm (2026-07-06 18:51:36 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm tags/mm-hotfixes-stable-2026-07-20-11-37
for you to fetch changes up to e57d6e9e20b551e4910d7a6331a81775c3ad6693:
mm/memory-failure: trace: change memory_failure_event to ras subsystem (2026-07-09 15:48:56 -0700)
----------------------------------------------------------------
12 hotfixes. 8 are cc:stable and the remainder address post-7.1 issues or
aren't considered appropriate for backporting. 10 are for MM.
All are singletons - please see the relevant changelogs for details.
----------------------------------------------------------------
Arnd Bergmann (1):
fat: avoid stack overflow warning
Breno Leitao (1):
mm/kmemleak: fix checksum computation for per-cpu objects
Lance Yang (1):
MAINTAINERS: add Usama as a THP reviewer
Michael S. Tsirkin (1):
mm: page_reporting: allow driver to set batch capacity
Mike Rapoport (Microsoft) (1):
userfaultfd: prevent registration of special VMAs
Rik van Riel (1):
mm/huge_memory: set PG_has_hwpoisoned only after new folio head is established
SJ Park (3):
MAINTAINERS: s/SeongJae/SJ/
mm/damon/core: validate ranges in damon_set_regions()
mm/damon/core: disallow overlapping input ranges for damon_set_regions()
Thomas Weißschuh (1):
m68k: avoid -Wunused-but-set-parameter in clear_user_page()
Wei Yang (1):
mm/page_vma_mapped: fix device-private PMD handling
Xie Yuanbin (1):
mm/memory-failure: trace: change memory_failure_event to ras subsystem
.mailmap | 1 +
Documentation/ABI/testing/sysfs-kernel-mm-damon | 174 ++++++++++++------------
MAINTAINERS | 3 +-
arch/m68k/include/asm/page_mm.h | 2 +
drivers/virtio/virtio_balloon.c | 5 +-
fs/fat/fat.h | 4 +-
fs/fat/fat_test.c | 4 +-
include/linux/damon.h | 2 -
include/linux/page_reporting.h | 4 +-
include/trace/events/memory-failure.h | 6 +-
mm/damon/core.c | 15 +-
mm/damon/lru_sort.c | 2 -
mm/damon/modules-common.c | 2 -
mm/damon/modules-common.h | 2 -
mm/damon/ops-common.c | 2 -
mm/damon/ops-common.h | 2 -
mm/damon/paddr.c | 2 -
mm/damon/reclaim.c | 2 -
mm/damon/sysfs-common.c | 2 -
mm/damon/sysfs-common.h | 2 -
mm/damon/sysfs-schemes.c | 2 -
mm/damon/sysfs.c | 2 -
mm/damon/tests/core-kunit.h | 4 -
mm/damon/tests/sysfs-kunit.h | 2 -
mm/damon/tests/vaddr-kunit.h | 4 -
mm/damon/vaddr.c | 2 -
mm/huge_memory.c | 12 +-
mm/kmemleak.c | 7 +-
mm/page_reporting.c | 24 ++--
mm/page_vma_mapped.c | 31 +++--
mm/userfaultfd.c | 5 +-
31 files changed, 163 insertions(+), 170 deletions(-)
next reply other threads:[~2026-07-20 18:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-20 18:39 Andrew Morton [this message]
2026-07-20 20:07 ` [GIT PULL] hotfixes for 7.2-rc5 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=20260720113947.6b43f86cede7f20c4126650b@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