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 5.18-rc7
Date: Fri, 13 May 2022 10:08:25 -0700 [thread overview]
Message-ID: <20220513100825.701c0801de7f18168c4d838c@linux-foundation.org> (raw)
Linus,
Please pull a bunch of hotfixes for 5.18-rc7.
The following changes since commit 38d741cb70b30741c0e802cbed7bd9cf4fd15fa4:
Merge tag 'drm-fixes-2022-04-29' of git://anongit.freedesktop.org/drm/drm (2022-04-28 18:00:34 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm tags/mm-hotfixes-stable-2022-05-11
for you to fetch changes up to 9039b8335276569670caaf23606335946625e764:
MAINTAINERS: add a mailing list for DAMON development (2022-05-09 17:34:29 -0700)
----------------------------------------------------------------
Seven MM fixes, three of which address issues added in the most recent
merge window, four of which are cc:stable.
Three non-MM fixes, none very serious.
----------------------------------------------------------------
Hyeonggon Yoo (1):
mm/kfence: reset PG_slab and memcg_data before freeing __kfence_pool
Joel Savitz (1):
selftests: vm: Makefile: rename TARGETS to VMTARGETS
Kalesh Singh (1):
procfs: prevent unprivileged processes accessing fdinfo dir
Martyna Szapar-Mudlaw (1):
mailmap: add entry for martyna.szapar-mudlaw@intel.com
Mike Rapoport (1):
arm[64]/memremap: don't abuse pfn_valid() to ensure presence of linear map
Naoya Horiguchi (1):
mm/hwpoison: use pr_err() instead of dump_page() in get_any_page()
Niels Dossche (1):
mm: mremap: fix sign for EFAULT error return value
SeongJae Park (1):
MAINTAINERS: add a mailing list for DAMON development
Xu Yu (2):
Revert "mm/memory-failure.c: skip huge_zero_page in memory_failure()"
mm/huge_memory: do not overkill when splitting huge_zero_page
.mailmap | 1 +
MAINTAINERS | 1 +
arch/arm/include/asm/io.h | 3 +++
arch/arm/mm/ioremap.c | 8 ++++++++
arch/arm64/include/asm/io.h | 4 ++++
arch/arm64/mm/ioremap.c | 8 ++++++++
fs/proc/fd.c | 23 ++++++++++++++++++++++-
mm/huge_memory.c | 7 ++++++-
mm/kfence/core.c | 10 ++++++++++
mm/memory-failure.c | 15 +--------------
mm/mremap.c | 2 +-
tools/testing/selftests/vm/Makefile | 10 +++++-----
12 files changed, 70 insertions(+), 22 deletions(-)
next reply other threads:[~2022-05-13 17:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 17:08 Andrew Morton [this message]
2022-05-13 17:27 ` Linus Torvalds
2022-05-13 17: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=20220513100825.701c0801de7f18168c4d838c@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