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.1 final
Date: Sat, 10 Dec 2022 17:03:17 -0800 [thread overview]
Message-ID: <20221210170317.130e7dbfc0e78de6067c4012@linux-foundation.org> (raw)
Linus, please merge this final batch of hotfixes for 6.1, thanks.
The following changes since commit 1d351f1894342c378b96bb9ed89f8debb1e24e9f:
revert "kbuild: fix -Wimplicit-function-declaration in license_is_gpl_compatible" (2022-11-30 14:49:42 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm tags/mm-hotfixes-stable-2022-12-10-1
for you to fetch changes up to 4a7ba45b1a435e7097ca0f79a847d0949d0eb088:
memcg: fix possible use-after-free in memcg_write_event_control() (2022-12-09 18:41:17 -0800)
----------------------------------------------------------------
9 hotfixes. 6 for MM, 3 for other areas. Four of these patches address
post-6.0 issues.
----------------------------------------------------------------
David Hildenbrand (1):
mm/swap: fix SWP_PFN_BITS with CONFIG_PHYS_ADDR_T_64BIT on 32bit
Hugh Dickins (1):
tmpfs: fix data loss from failed fallocate
Jason A. Donenfeld (1):
mm: do not BUG_ON missing brk mapping, because userspace can unmap it
John Starks (1):
mm/gup: fix gup_pud_range() for dax
Liam Howlett (1):
mmap: fix do_brk_flags() modifying obviously incorrect VMAs
Matti Vaittinen (1):
mailmap: update Matti Vaittinen's email address
Michal Hocko (1):
kselftests: cgroup: update kmem test precision tolerance
Muchun Song (1):
MAINTAINERS: update Muchun Song's email
Tejun Heo (1):
memcg: fix possible use-after-free in memcg_write_event_control()
.mailmap | 3 +++
MAINTAINERS | 4 ++--
include/linux/cgroup.h | 1 +
include/linux/swapops.h | 8 +++++---
kernel/cgroup/cgroup-internal.h | 1 -
mm/gup.c | 2 +-
mm/memcontrol.c | 15 +++++++++++++--
mm/mmap.c | 14 ++++----------
mm/shmem.c | 11 +++++++++++
tools/testing/selftests/cgroup/test_kmem.c | 6 +++---
10 files changed, 43 insertions(+), 22 deletions(-)
next reply other threads:[~2022-12-11 1:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-11 1:03 Andrew Morton [this message]
2022-12-11 1:15 ` [GIT PULL] hotfixes for 6.1 final Linus Torvalds
2022-12-11 1:16 ` 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=20221210170317.130e7dbfc0e78de6067c4012@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.