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.10-rc1
Date: Sat, 25 May 2024 09:15:57 -0700 [thread overview]
Message-ID: <20240525091557.9ca6e57ab6d41bf204c12531@linux-foundation.org> (raw)
Linus, please merge this batch of nilfs2 and mm/ hotfixes, thanks.
The following changes since commit c760b3725e52403dc1b28644fb09c47a83cacea6:
Merge tag 'mm-nonmm-stable-2024-05-22-17-30' of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm (2024-05-22 18:59:29 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm tags/mm-hotfixes-stable-2024-05-25-09-13
for you to fetch changes up to 90e823498881fb8a91d83e9a8eed87c8c3ff2176:
mm/ksm: fix possible UAF of stable_node (2024-05-24 11:55:08 -0700)
----------------------------------------------------------------
16 hotfixes, 11 of which are cc:stable.
A few nilfs2 fixes, the remainder are for MM: a couple of selftests fixes,
various singletons fixing various issues in various parts.
----------------------------------------------------------------
Andrey Konovalov (1):
kasan, fortify: properly rename memintrinsics
Chengming Zhou (1):
mm/ksm: fix possible UAF of stable_node
Dev Jain (3):
selftests/mm: compaction_test: fix bogus test success on Aarch64
selftests/mm: compaction_test: fix incorrect write of zero to nr_hugepages
selftests/mm: compaction_test: fix bogus test success and reduce probability of OOM-killer invocation
Hailong.Liu (1):
mm/vmalloc: fix vmalloc which may return null if called with __GFP_NOFAIL
Miaohe Lin (2):
mm/huge_memory: don't unpoison huge_zero_folio
mm/memory-failure: fix handling of dissolved but not taken off from buddy pages
Michael Ellerman (1):
selftests/mm: fix build warnings on ppc64
Ryusuke Konishi (3):
nilfs2: fix use-after-free of timer for log writer thread
nilfs2: fix unexpected freezing of nilfs_segctor_sync()
nilfs2: fix potential hang in nilfs_detach_log_writer()
Satya Priya Kakitapalli (1):
mailmap: update email address for Satya Priya
Suren Baghdasaryan (1):
lib: add version into /proc/allocinfo output
Will Deacon (1):
arm64: patching: fix handling of execmem addresses
Yuanyuan Zhong (1):
mm: /proc/pid/smaps_rollup: avoid skipping vma after getting mmap_lock again
.mailmap | 2 +-
Documentation/filesystems/proc.rst | 5 +-
arch/arm64/kernel/patching.c | 2 +-
fs/nilfs2/segment.c | 63 ++++++++++++++++-----
fs/proc/task_mmu.c | 9 ++-
include/linux/fortify-string.h | 22 +++++--
lib/alloc_tag.c | 47 ++++++++++-----
mm/ksm.c | 3 +-
mm/memory-failure.c | 11 +++-
mm/vmalloc.c | 5 +-
tools/testing/selftests/mm/compaction_test.c | 85 ++++++++++++++++++++--------
tools/testing/selftests/mm/gup_test.c | 1 +
tools/testing/selftests/mm/uffd-common.h | 1 +
13 files changed, 187 insertions(+), 69 deletions(-)
next reply other threads:[~2024-05-25 16:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-25 16:15 Andrew Morton [this message]
2024-05-25 22:25 ` 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=20240525091557.9ca6e57ab6d41bf204c12531@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