From: Tarun Sahu <tarunsahu@google.com>
To: Andrew Morton <akpm@linux-foundation.org>,
Pasha Tatashin <pasha.tatashin@soleen.com>,
Alexander Graf <graf@amazon.com>,
Pratyush Yadav <pratyush@kernel.org>,
Mike Rapoport <rppt@kernel.org>
Cc: linux-kernel@vger.kernel.org, kexec@lists.infradead.org,
linux-mm@kvack.org, Tarun Sahu <tarunsahu@google.com>
Subject: [RESEND PATCH v3 0/2] luo: convert serialized ptr to KHOSER_PTR
Date: Mon, 22 Jun 2026 11:12:13 +0000 [thread overview]
Message-ID: <20260622111215.4157974-1-tarunsahu@google.com> (raw)
Convert raw serialized_data to KHO serializeable pointer (KHOSER_PTR).
This series also takes care of resolving the bug with memfd of using
phys_to_virt before checking the args->serialized_data value.
RESEND V3:
Sent incorrect thread format earlier, this one is with correct
one.
v3 <- v2
Rebased on top of liveupdate/next
v2 <- v1
Use KHOSER_PTR across liveupdate files instead of only memfd_luo
Tarun Sahu (2):
kho: add KHOSER_COPY_TYPE(UN)SAFE for phys copy
luo: Update serialized data to use KHOSER_PTR
include/linux/kho/abi/kexec_handover.h | 12 ++++++++++++
include/linux/kho/abi/luo.h | 5 +++--
include/linux/liveupdate.h | 4 ++--
kernel/liveupdate/luo_file.c | 24 ++++++++++++------------
mm/memfd_luo.c | 18 +++++++++---------
5 files changed, 38 insertions(+), 25 deletions(-)
base-commit: e98a9c61721c14bcd29f11f4802e52e908701f7a
--
2.55.0.rc0.738.g0c8ab3ebcc-goog
next reply other threads:[~2026-06-22 11:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-22 11:12 Tarun Sahu [this message]
2026-06-22 11:12 ` [RESEND PATCH v3 1/2] kho: add KHOSER_COPY_TYPE(UN)SAFE for phys copy Tarun Sahu
2026-06-22 11:12 ` [REESND PATCH v3 2/2] luo: Update serialized data to use KHOSER_PTR Tarun Sahu
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=20260622111215.4157974-1-tarunsahu@google.com \
--to=tarunsahu@google.com \
--cc=akpm@linux-foundation.org \
--cc=graf@amazon.com \
--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=rppt@kernel.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