From: sashiko-bot@kernel.org
To: "Tarun Sahu" <tarunsahu@google.com>
Cc: kvm@vger.kernel.org, "Marc Zyngier" <maz@kernel.org>,
kvmarm@lists.linux.dev, "Oliver Upton" <oupton@kernel.org>
Subject: Re: [PATCH v4 01/11] liveupdate: Add LIVEUPDATE_GUEST_MEMFD config option
Date: Tue, 28 Jul 2026 12:22:45 +0000 [thread overview]
Message-ID: <20260728122245.AA83D1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260728121138.1103610-2-tarunsahu@google.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The patch introduces the `LIVEUPDATE_GUEST_MEMFD` Kconfig option claiming to enable a new feature, but there is no actual implementation provided.
--
--- Patch [1]: [PATCH v4 01/11] liveupdate: Add LIVEUPDATE_GUEST_MEMFD config option ---
commit e0c3fde657d56c548cd9a7467d2143f0f42c5242
Author: Tarun Sahu <tarunsahu@google.com>
liveupdate: Add LIVEUPDATE_GUEST_MEMFD config option
This commit introduces the LIVEUPDATE_GUEST_MEMFD Kconfig option, which aims
to enable live update support for KVM guest_memfd files.
> diff --git a/kernel/liveupdate/Kconfig b/kernel/liveupdate/Kconfig
> index 1a8513f16ef7c..0bbc4037192e9 100644
> --- a/kernel/liveupdate/Kconfig
> +++ b/kernel/liveupdate/Kconfig
> @@ -88,4 +88,19 @@ config LIVEUPDATE_MEMFD
>
> If unsure, say N.
>
> +config LIVEUPDATE_GUEST_MEMFD
> + bool "Live update support for guest_memfd"
> + depends on LIVEUPDATE
> + depends on KVM_GUEST_MEMFD
> + default LIVEUPDATE
[Severity: Medium]
Is the implementation for this feature missing from this patch?
The commit message notes that this patch enables live update support for KVM
guest_memfd files, but the newly added LIVEUPDATE_GUEST_MEMFD symbol appears
to be unreferenced in the tree. Since there are no Makefiles, C files, or
preprocessor checks that use it, this currently acts as dead code.
Could the implementation be missing, or was this intended to be introduced as
part of a larger series where the symbol is used in a subsequent patch?
> + help
> + Enable live update support for KVM guest_memfd files. This allows
> + preserving VM Memory backed by guest_memfd file across kernel live
> + updates.
> +
> + This can only be used for the guest_memfd that are fully-shared
> + and pre-faulted.
> +
> + If unsure, say N.
> +
> endmenu
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260728121138.1103610-1-tarunsahu@google.com?part=1
next prev parent reply other threads:[~2026-07-28 12:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-28 12:11 [PATCH v4 00/11] liveupdate: kvm: Guest_memfd preservation Tarun Sahu
2026-07-28 12:11 ` [PATCH v4 01/11] liveupdate: Add LIVEUPDATE_GUEST_MEMFD config option Tarun Sahu
2026-07-28 12:22 ` sashiko-bot [this message]
2026-07-28 12:11 ` [PATCH v4 02/11] KVM: Introduce kvm_create_vm_file() helper Tarun Sahu
2026-07-28 12:11 ` [PATCH v4 03/11] KVM: Export kvm_uevent_notify_vm_create() Tarun Sahu
2026-07-28 12:26 ` sashiko-bot
2026-07-28 12:11 ` [PATCH v4 04/11] KVM: Track weak reference to vm_file in struct kvm Tarun Sahu
2026-07-28 12:11 ` [PATCH v4 05/11] KVM: LUO: Support VM preservation across live updates Tarun Sahu
2026-07-28 12:27 ` sashiko-bot
2026-07-28 12:11 ` [PATCH v4 06/11] KVM: guest_memfd: Move internal definitions to internal header Tarun Sahu
2026-07-28 12:11 ` [PATCH v4 07/11] KVM: guest_memfd: Add support for freezing mappings Tarun Sahu
2026-07-28 12:20 ` sashiko-bot
2026-07-28 12:11 ` [PATCH v4 08/11] KVM: guest_memfd: Add support for preservation via LUO Tarun Sahu
2026-07-28 12:23 ` sashiko-bot
2026-07-28 12:11 ` [PATCH v4 09/11] docs: liveupdate: Add documentation for VM and guest_memfd preservation Tarun Sahu
2026-07-28 12:21 ` sashiko-bot
2026-07-28 12:11 ` [PATCH v4 10/11] KVM: selftests: Split ____vm_create() and add vm_create_from_fd() Tarun Sahu
2026-07-28 12:11 ` [PATCH v4 11/11] KVM: selftests: Add guest_memfd_preservation_test 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=20260728122245.AA83D1F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=maz@kernel.org \
--cc=oupton@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=tarunsahu@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