From: Tarun Sahu <tarunsahu@google.com>
To: Pasha Tatashin <pasha.tatashin@soleen.com>,
Pratyush Yadav <pratyush@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, Mike Rapoport <rppt@kernel.org>,
Alexander Graf <graf@amazon.com>,
skhawaja@google.com
Cc: kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
Tarun Sahu <tarunsahu@google.com>
Subject: [PATCH v6 0/3] luo: convert serialized ptr to KHOSER_PTR
Date: Sun, 28 Jun 2026 00:11:11 +0000 [thread overview]
Message-ID: <20260628001114.1869564-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.
Tested ./luo_kexec_simple --stage 1 && 2
v6 <- v5
-Compilation error fix
-Nit comment fixes
v5 <- v4
-separate the memfd_luo fix in a new commit to allow backport if
needed.
v4 <- RESEND V3
-use only KHOSER_COPY_PTR and have compiler time check for type
excluding void * types. Remove TYPE(UN)SAFE variants.
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 (3):
mm/memfd_luo: validate serialized_data before conversion
kho: add KHOSER_COPY_PTR to allow phys copy of serialized ptr
luo: Update serialized data to use KHOSER_PTR
include/linux/kho/abi/kexec_handover.h | 11 +++++++++++
include/linux/kho/abi/luo.h | 5 +++--
include/linux/liveupdate.h | 4 ++--
kernel/liveupdate/luo_file.c | 24 ++++++++++++------------
mm/memfd_luo.c | 16 +++++++---------
5 files changed, 35 insertions(+), 25 deletions(-)
base-commit: e98a9c61721c14bcd29f11f4802e52e908701f7a
--
2.55.0.rc0.799.gd6f94ed593-goog
next reply other threads:[~2026-06-28 0:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-28 0:11 Tarun Sahu [this message]
2026-06-28 0:11 ` [PATCH v6 1/3] mm/memfd_luo: validate serialized_data before conversion Tarun Sahu
2026-06-28 0:11 ` [PATCH v6 2/3] kho: add KHOSER_COPY_PTR to allow phys copy of serialized ptr Tarun Sahu
2026-06-28 0:11 ` [PATCH v6 3/3] luo: Update serialized data to use KHOSER_PTR Tarun Sahu
2026-06-29 7:01 ` Pasha Tatashin
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=20260628001114.1869564-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 \
--cc=skhawaja@google.com \
/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