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 against 6.19-rc8
Date: Wed, 4 Feb 2026 15:58:38 -0800 [thread overview]
Message-ID: <20260204155838.05fd9b9d9b43b493fd0b74a4@linux-foundation.org> (raw)
Linus, please pull this small batch of hotfixes, thanks.
The following changes since commit bd58782995a2e6a07fd07255f3cc319f40b131c9:
vmcoreinfo: make hwerr_data visible for debugging (2026-01-26 19:03:49 -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-04-15-55
for you to fetch changes up to 1a47837bfafed7e9ef93f5dfdea6d70869b0c3ab:
Documentation: document liveupdate cmdline parameter (2026-02-02 18:43:56 -0800)
----------------------------------------------------------------
5 hotfixes. 2 are cc:stable, 2 are for MM.
All are singletons - please see the changelogs for details.
----------------------------------------------------------------
Alexander Mikhalitsyn (1):
mailmap: update Alexander Mikhalitsyn's emails
Andrew Cooper (1):
x86/kfence: fix booting on 32bit non-PAE systems
Kairui Song (1):
mm, shmem: prevent infinite loop on truncate race
Li Chen (1):
Documentation: document liveupdate cmdline parameter
Pratyush Yadav (Google) (1):
liveupdate: luo_file: do not clear serialized_data on unfreeze
.mailmap | 1 +
Documentation/admin-guide/kernel-parameters.txt | 5 +++++
arch/x86/include/asm/kfence.h | 7 ++++---
kernel/liveupdate/luo_file.c | 2 --
mm/shmem.c | 23 ++++++++++++++---------
5 files changed, 24 insertions(+), 14 deletions(-)
next reply other threads:[~2026-02-04 23:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 23:58 Andrew Morton [this message]
2026-02-05 17:47 ` 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=20260204155838.05fd9b9d9b43b493fd0b74a4@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