From: Andrew Morton <akpm@linux-foundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
mm-commits@vger.kernel.org
Subject: [GIT PULL] hotfixes against 6.14-rc7
Date: Mon, 17 Mar 2025 20:12:06 -0700 [thread overview]
Message-ID: <20250317201206.7800aeeb5dad94c230fe1456@linux-foundation.org> (raw)
Linus, please merge this batch of hotfixes, thanks.
The following changes since commit 80e54e84911a923c40d7bee33a34c1b4be148d7a:
Linux 6.14-rc6 (2025-03-09 13:45:25 -1000)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm tags/mm-hotfixes-stable-2025-03-17-20-09
for you to fetch changes up to 800f1059c99e2b39899bdc67a7593a7bea6375d8:
mm/page_alloc: fix memory accept before watermarks gets initialized (2025-03-16 17:40:26 -0700)
----------------------------------------------------------------
15 hotfixes. 7 are cc:stable and the remainder address post-6.13 issues
or aren't considered necessary for -stable kernels.
13 are for MM and the other two are for squashfs and procfs.
All are singletons. Please see the individual changelogs for details.
----------------------------------------------------------------
Dave Hansen (1):
filemap: move prefaulting out of hot write path
Dev Jain (1):
mm/vma: do not register private-anon mappings with khugepaged during mmap
Jinjiang Tu (1):
mm/hugetlb: fix surplus pages in dissolve_free_huge_page()
Kirill A. Shutemov (1):
mm/page_alloc: fix memory accept before watermarks gets initialized
Matthew Wilcox (Oracle) (1):
mm: decline to manipulate the refcount on a slab page
Muchun Song (1):
mm: memcontrol: fix swap counter leak from offline cgroup
Rafael Aquini (1):
selftests/mm: run_vmtests.sh: fix half_ufd_size_MB calculation
Raphael S. Carvalho (1):
mm: fix error handling in __filemap_get_folio() with FGP_NOWAIT
SeongJae Park (2):
mm/damon: respect core layer filters' allowance decision on ops layer
mm/damon/core: initialize damos->walk_completed in damon_new_scheme()
Shakeel Butt (1):
memcg: drain obj stock on cpu hotplug teardown
Ye Bin (1):
proc: fix UAF in proc_get_inode()
Zhiyu Zhang (1):
squashfs: fix invalid pointer dereference in squashfs_cache_delete
Zi Yan (2):
mm/migrate: fix shmem xarray update during migration
mm/huge_memory: drop beyond-EOF folios with the right number of refs
fs/proc/generic.c | 10 +++++++-
fs/proc/inode.c | 6 ++---
fs/proc/internal.h | 14 +++++++++++
fs/squashfs/cache.c | 2 +-
include/linux/damon.h | 5 ++++
include/linux/mm.h | 8 ++++++-
include/linux/proc_fs.h | 7 ++++--
include/linux/swap_cgroup.h | 4 ++--
lib/iov_iter.c | 8 +++++--
mm/damon/core.c | 7 +++++-
mm/damon/paddr.c | 3 +++
mm/filemap.c | 40 +++++++++++++++++++++----------
mm/huge_memory.c | 2 +-
mm/hugetlb.c | 8 +++++--
mm/memcontrol.c | 13 ++++++++--
mm/migrate.c | 10 ++++----
mm/page_alloc.c | 14 +++++++++--
mm/swap_cgroup.c | 7 +++---
mm/vma.c | 3 ++-
tools/testing/selftests/mm/run_vmtests.sh | 4 +++-
20 files changed, 132 insertions(+), 43 deletions(-)
next reply other threads:[~2025-03-18 3:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 3:12 Andrew Morton [this message]
2025-03-18 5:56 ` 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=20250317201206.7800aeeb5dad94c230fe1456@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