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.4-rc1
Date: Wed, 3 May 2023 16:24:32 -0700 [thread overview]
Message-ID: <20230503162432.24a580b6c1a7fd465ed6bc2d@linux-foundation.org> (raw)
Linus, please merge this small batch or MM updates, thanks.
The following changes since commit 22b8cc3e78f5448b4c5df00303817a9137cd663f:
Merge tag 'x86_mm_for_6.4' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip (2023-04-28 09:43:49 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm tags/mm-stable-2023-05-03-16-22
for you to fetch changes up to 245f0922689364b21163af4937a05ea0ba576fae:
mm: hwpoison: coredump: support recovery from dump_user_range() (2023-05-02 17:21:50 -0700)
----------------------------------------------------------------
- Some DAMON cleanups from Kefeng Wang
- Some KSM work from David Hildenbrand, to make the PR_SET_MEMORY_MERGE
ioctl's behavior more similar to KSM's behavior.
----------------------------------------------------------------
Baolin Wang (1):
mm/page_alloc: add some comments to explain the possible hole in __pageblock_pfn_to_page()
David Hildenbrand (3):
mm/ksm: unmerge and clear VM_MERGEABLE when setting PR_SET_MEMORY_MERGE=0
selftests/ksm: ksm_functional_tests: add prctl unmerge test
mm/ksm: move disabling KSM from s390/gmap code to KSM code
Kefeng Wang (4):
mm/damon/paddr: minor refactor of damon_pa_pageout()
mm/damon/paddr: minor refactor of damon_pa_mark_accessed_or_deactivate()
mm/damon/paddr: fix missing folio_sz update in damon_pa_young()
mm: hwpoison: coredump: support recovery from dump_user_range()
arch/s390/mm/gmap.c | 20 +------
fs/coredump.c | 1 +
include/linux/ksm.h | 7 +++
include/linux/uio.h | 16 ++++++
kernel/sys.c | 12 +---
lib/iov_iter.c | 17 +++++-
mm/damon/paddr.c | 26 ++++-----
mm/ksm.c | 70 +++++++++++++++++++++++
mm/page_alloc.c | 9 +++
tools/testing/selftests/mm/ksm_functional_tests.c | 46 +++++++++++++--
10 files changed, 172 insertions(+), 52 deletions(-)
next reply other threads:[~2023-05-03 23:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-03 23:24 Andrew Morton [this message]
2023-05-04 20: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=20230503162432.24a580b6c1a7fd465ed6bc2d@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