From: Andrew Morton <akpm@linux-foundation.org>
To: Linus Torvalds <torvalds@linuxfoundation.org>
Cc: linux-mm@kvack.org, mm-commits@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [GIT PULL] more hotfixes against 6.19-rc8
Date: Fri, 6 Feb 2026 12:43:41 -0800 [thread overview]
Message-ID: <20260206124341.c7dc8fc55e0f0f9ea68d3951@linux-foundation.org> (raw)
Linus, please merge these two MM fixes for the upcoming release, thanks.
The following changes since commit 1a47837bfafed7e9ef93f5dfdea6d70869b0c3ab:
Documentation: document liveupdate cmdline parameter (2026-02-02 18:43:56 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm tags/mm-hotfixes-stable-2026-02-06-12-37
for you to fetch changes up to ae9fd76c111bb4a5293c2831a1ad373605251dd6:
mm/memory-failure: reject unsupported non-folio compound page (2026-02-05 14:10:00 -0800)
----------------------------------------------------------------
A couple of late-breaking MM fixes. One against a new-in-this-cycle patch
and the other addresses a locking issue which has been there for 1+ years.
----------------------------------------------------------------
Andrii Nakryiko (1):
procfs: avoid fetching build ID while holding VMA lock
Miaohe Lin (1):
mm/memory-failure: reject unsupported non-folio compound page
fs/proc/task_mmu.c | 42 +++++++++++++++++++++++++++---------------
include/linux/buildid.h | 3 +++
lib/buildid.c | 42 ++++++++++++++++++++++++++++++------------
mm/memory-failure.c | 42 ++++++++++++++++++++----------------------
4 files changed, 80 insertions(+), 49 deletions(-)
next reply other threads:[~2026-02-06 20:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-06 20:43 Andrew Morton [this message]
2026-02-06 23:09 ` 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=20260206124341.c7dc8fc55e0f0f9ea68d3951@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@linuxfoundation.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