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 5.19-rcX
Date: Sun, 26 Jun 2022 12:53:10 -0700 [thread overview]
Message-ID: <20220626125310.83a3f4bb1b38bf9408d7c42c@linux-foundation.org> (raw)
Linus,
please merge this batch of hotfixes.
The following changes since commit b13baccc3850ca8b8cccbf8ed9912dbaa0fdf7f3:
Linux 5.19-rc2 (2022-06-12 16:11:37 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm tags/mm-hotfixes-stable-2022-06-26
for you to fetch changes up to e67679cc4264cf9b318af4e8616eaa2a7565db1f:
mailmap: add entry for Christian Marangi (2022-06-16 19:11:32 -0700)
----------------------------------------------------------------
Minor things, mainly - mailmap updates, MAINTAINERS updates, etc.
Fixes for post-5.18 changes:
- fix for a damon boot hang, from SeongJae
- fix for a kfence warning splat, from Jason Donenfeld
- fix for zero-pfn pinning, from Alex Williamson
- fix for fallocate hole punch clearing, from Mike Kravetz
Fixes pre-5.18 material:
- fix for a performance regression, from Marcelo
- fix for a hwpoisining BUG from zhenwei pi
----------------------------------------------------------------
Abel Vesa (1):
MAINTAINERS: update Abel Vesa's email
Alex Williamson (1):
mm: re-allow pinning of zero pfns
Andrew Morton (1):
MAINTAINERS: update MM tree references
Christian Marangi (1):
mailmap: add entry for Christian Marangi
David Hildenbrand (1):
MAINTAINERS: add MEMORY HOT(UN)PLUG section and add David as reviewer
Huacai Chen (1):
MAINTAINERS: add maillist information for LoongArch
Jarkko Sakkinen (1):
mailmap: add alias for jarkko@profian.com
Jason A. Donenfeld (1):
mm/kfence: select random number before taking raw lock
Marcelo Tosatti (1):
mm: lru_cache_disable: use synchronize_rcu_expedited
Miaohe Lin (1):
MAINTAINERS: add Miaohe Lin as a memory-failure reviewer
Mike Kravetz (1):
hugetlbfs: zero partial pages during fallocate hole punch
Petr Mladek (1):
kthread: make it clear that kthread_create_on_node() might be terminated by any fatal signal
SeongJae Park (1):
mm/damon/reclaim: schedule 'damon_reclaim_timer' only after 'system_wq' is initialized
Yang Li (1):
mm/page_isolation.c: fix one kernel-doc comment
Yang Yang (1):
mm: memcontrol: reference to tools/cgroup/memcg_slabinfo.py
zhenwei pi (1):
mm/memory-failure: disable unpoison once hw error happens
.mailmap | 4 +++
Documentation/vm/hwpoison.rst | 3 +-
MAINTAINERS | 21 ++++++++++---
drivers/base/memory.c | 2 +-
fs/hugetlbfs/inode.c | 68 +++++++++++++++++++++++++++++++++----------
include/linux/mm.h | 3 +-
kernel/kthread.c | 14 ++++-----
mm/damon/reclaim.c | 8 +++++
mm/hwpoison-inject.c | 2 +-
mm/kfence/core.c | 7 +++--
mm/madvise.c | 2 +-
mm/memcontrol.c | 2 +-
mm/memory-failure.c | 12 ++++++++
mm/page_isolation.c | 2 ++
mm/swap.c | 2 +-
15 files changed, 117 insertions(+), 35 deletions(-)
next reply other threads:[~2022-06-26 19:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-26 19:53 Andrew Morton [this message]
2022-06-26 21:29 ` 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=20220626125310.83a3f4bb1b38bf9408d7c42c@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