From: Mike Rapoport <rppt@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
David Carlier <devnexen@gmail.com>,
Evangelos Petrongonas <epetron@amazon.de>,
Mike Rapoport <rppt@kernel.org>,
Pasha Tatashin <pasha.tatashin@soleen.com>,
Pratyush Yadav <pratyush@kernel.org>,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: [GIT PULL] liveupdate updates for v7.1-rc4
Date: Wed, 13 May 2026 13:22:18 +0300 [thread overview]
Message-ID: <agRQ2pV1vsO-MoTB@kernel.org> (raw)
Hi Linus,
The following changes since commit 254f49634ee16a731174d2ae34bc50bd5f45e731:
Linux 7.1-rc1 (2026-04-26 14:19:00 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/liveupdate/linux.git tags/fixes-2026-05-13
for you to fetch changes up to 7b0b68b2b95606e65594958686833e53423f58f2:
mm/memfd_luo: document preservation of file seals (2026-05-04 14:03:16 +0000)
----------------------------------------------------------------
liveupdate fixes for v7.1-rc4
A few fixes for kexec handover and liveupdate:
* make sure KHO is skipped for crash kernel
* fix error reporting in memfd preservation if it fails mid-loop
* don't allow preserving memfds whose page count exceeds UINT_MAX
* fix documentation of memfd seals preservation to match the code
----------------------------------------------------------------
David Carlier (3):
mm/memfd_luo: report error when restoring a folio fails mid-loop
mm/memfd_luo: reject memfds whose page count exceeds UINT_MAX
mm/memfd_luo: document preservation of file seals
Evangelos Petrongonas (1):
kho: skip KHO for crash kernel
kernel/liveupdate/kexec_handover.c | 2 +-
mm/memfd_luo.c | 25 +++++++++++++++++++------
2 files changed, 20 insertions(+), 7 deletions(-)
--
Sincerely yours,
Mike.
reply other threads:[~2026-05-13 10:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=agRQ2pV1vsO-MoTB@kernel.org \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=devnexen@gmail.com \
--cc=epetron@amazon.de \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pasha.tatashin@soleen.com \
--cc=pratyush@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