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] Final MM updates for 6.16-rc1
Date: Fri, 6 Jun 2025 16:12:31 -0700 [thread overview]
Message-ID: <20250606161231.c9e10415b320f8cbc7006d26@linux-foundation.org> (raw)
Linus, please merge this single bugfix series for this -rc cycle, thanks.
The following changes since commit 546b1c9e93c2bb8cf5ed24e0be1c86bb089b3253:
Merge tag 'bootconfig-v6.16' of git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace (2025-06-02 17:39:24 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm tags/mm-stable-2025-06-06-16-09
for you to fetch changes up to efe99fabeb11b030c89a7dc5a5e7a7558d0dc7ec:
selftests/mm: add test about uprobe pte be orphan during vma merge (2025-06-05 21:55:42 -0700)
----------------------------------------------------------------
- The 4 patch series "Fix uprobe pte be overwritten when expanding vma"
fixes a longstanding and quite obscure bug related to the vma merging of
the uprobe mmap page.
----------------------------------------------------------------
Enze Li (1):
mm/damon: s/primitives/code/ on comments
Pu Lehui (4):
mm: fix uprobe pte be overwritten when expanding vma
mm: expose abnormal new_pte during move_ptes
selftests/mm: extract read_sysfs and write_sysfs into vm_util
selftests/mm: add test about uprobe pte be orphan during vma merge
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/sysfs-common.c | 2 +-
mm/damon/sysfs-common.h | 2 +-
mm/damon/vaddr.c | 2 +-
mm/mremap.c | 2 ++
mm/vma.c | 20 +++++++++++++---
mm/vma.h | 7 ++++++
tools/testing/selftests/mm/ksm_tests.c | 32 ++-----------------------
tools/testing/selftests/mm/merge.c | 43 ++++++++++++++++++++++++++++++++++
tools/testing/selftests/mm/thuge-gen.c | 6 ++---
tools/testing/selftests/mm/vm_util.c | 38 ++++++++++++++++++++++++++++++
tools/testing/selftests/mm/vm_util.h | 2 ++
16 files changed, 122 insertions(+), 44 deletions(-)
next reply other threads:[~2025-06-06 23:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-06 23:12 Andrew Morton [this message]
2025-06-07 5:11 ` 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=20250606161231.c9e10415b320f8cbc7006d26@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