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 for 6.9-rc3
Date: Fri, 5 Apr 2024 11:40:18 -0700 [thread overview]
Message-ID: <20240405114018.48d320803e1b3920f68f9f96@linux-foundation.org> (raw)
Linus, please merge this batch of hotfixes.
There's a simple conflict in MAINTAINERS. Please take the changes from
this tree - use the four broadcom email addresses.
Thanks.
The following changes since commit 39cd87c4eb2b893354f3b850f916353f2658ae6f:
Linux 6.9-rc2 (2024-03-31 14:32:39 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm tags/mm-hotfixes-stable-2024-04-05-11-30
for you to fetch changes up to a6c1d9cb9a68bfa4512248419c4f4d880d19fe90:
stackdepot: rename pool_index to pool_index_plus_1 (2024-04-05 11:21:31 -0700)
----------------------------------------------------------------
8 hotfixes, 3 are cc:stable
There are a couple of fixups for this cycle's vmalloc changes and one for
the stackdepot changes. And a fix for a very old x86 PAT issue which can
cause a warning splat.
----------------------------------------------------------------
Alexey Makhalov (1):
MAINTAINERS: change vmware.com addresses to broadcom.com
David Hildenbrand (2):
mm/secretmem: fix GUP-fast succeeding on secretmem folios
x86/mm/pat: fix VM_PAT handling in COW mappings
Edward Liaw (1):
selftests/mm: include strings.h for ffsl
John Sperbeck (1):
init: open output files from cpio unpacking with O_LARGEFILE
Peter Collingbourne (1):
stackdepot: rename pool_index to pool_index_plus_1
Uladzislau Rezki (Sony) (2):
mm: vmalloc: bail out early in find_vmap_area() if vmap is not init
mm: vmalloc: fix lockdep warning
.mailmap | 5 +++
MAINTAINERS | 46 +++++++++++-----------
arch/x86/mm/pat/memtype.c | 49 ++++++++++++++++-------
include/linux/secretmem.h | 4 +-
include/linux/stackdepot.h | 7 ++--
init/initramfs.c | 2 +-
lib/stackdepot.c | 4 +-
mm/memory.c | 4 ++
mm/vmalloc.c | 76 ++++++++++++++++++++++--------------
tools/testing/selftests/mm/vm_util.h | 2 +-
10 files changed, 122 insertions(+), 77 deletions(-)
next reply other threads:[~2024-04-05 18:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-05 18:40 Andrew Morton [this message]
2024-04-05 21:05 ` 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=20240405114018.48d320803e1b3920f68f9f96@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