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,
Suren Baghdasaryan <surenb@google.com>
Subject: [GIT PULL] hotfixes for 6.5-rc1
Date: Sat, 8 Jul 2023 10:46:58 -0700 [thread overview]
Message-ID: <20230708104658.927e647f75d55c4a5d99cbf5@linux-foundation.org> (raw)
Linus, please merge this batch of hotfixes, thanks.
This includes the disabling of the CONFIG_PER_VMA_LOCK feature, which
needs some additional work before being suitable for use.
The following changes since commit 3fbff91afbf0148e937b8718ed865b073c587d9f:
Merge branch 'master' into mm-hotfixes-stable (2023-07-02 18:53:03 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm tags/mm-hotfixes-stable-2023-07-08-10-43
for you to fetch changes up to 8ba388c06bc8056935ec1814b2689bfb42f3b89a:
lib: dhry: fix sleeping allocations inside non-preemptable section (2023-07-08 09:29:32 -0700)
----------------------------------------------------------------
16 hotfixes. Six are cc:stable and the remainder address post-6.4 issues.
----------------------------------------------------------------
Andrey Konovalov (2):
kasan: fix type cast in memory_is_poisoned_n
kasan, slub: fix HW_TAGS zeroing with slub_debug
Anthony Iliopoulos (2):
MAINTAINERS: update ocfs2-devel mailing list address
docs: update ocfs2-devel mailing list address
Geert Uytterhoeven (1):
lib: dhry: fix sleeping allocations inside non-preemptable section
Heiko Stuebner (2):
mailmap: update manpage link
mailmap: add entries for Heiko Stuebner
John Hubbard (1):
mm/hugetlb.c: fix a bug within a BUG(): inconsistent pte comparison
Liu Shixin (1):
bootmem: remove the vmemmap pages from kmemleak in free_bootmem_page
Markus Schneider-Pargmann (1):
mailmap: add Markus Schneider-Pargmann
Matthew Wilcox (Oracle) (1):
writeback: account the number of pages written back
Peter Collingbourne (1):
mm: call arch_swap_restore() from do_swap_page()
Randy Dunlap (1):
MAINTAINERS: add linux-next info
Suren Baghdasaryan (2):
fork: lock VMAs of the parent process when forking
mm: disable CONFIG_PER_VMA_LOCK until its fixed
Vincent Whitchurch (1):
squashfs: fix cache race with migration
.mailmap | 7 ++++++-
Documentation/ABI/obsolete/o2cb | 4 ++--
Documentation/ABI/removed/o2cb | 4 ++--
Documentation/ABI/stable/o2cb | 4 ++--
Documentation/ABI/testing/sysfs-ocfs2 | 12 ++++++------
Documentation/filesystems/dlmfs.rst | 2 +-
Documentation/filesystems/ocfs2.rst | 2 +-
MAINTAINERS | 9 ++++++++-
fs/ocfs2/Kconfig | 6 +++---
fs/squashfs/block.c | 27 +++++++++++++++++++++++----
include/linux/bootmem_info.h | 2 ++
kernel/fork.c | 6 ++++++
lib/dhry_1.c | 11 +++++++++--
mm/Kconfig | 3 ++-
mm/hugetlb.c | 7 ++++++-
mm/kasan/generic.c | 3 ++-
mm/kasan/kasan.h | 12 ------------
mm/memory.c | 7 +++++++
mm/page-writeback.c | 8 +++++---
mm/slab.h | 16 ++++++++++++++--
20 files changed, 107 insertions(+), 45 deletions(-)
next reply other threads:[~2023-07-08 17:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-08 17:46 Andrew Morton [this message]
2023-07-08 21:41 ` 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=20230708104658.927e647f75d55c4a5d99cbf5@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=surenb@google.com \
--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