From: Mike Rapoport <rppt@kernel.org>
To: Breno Leitao <leitao@debian.org>
Cc: Alexander Graf <graf@amazon.com>,
Pasha Tatashin <pasha.tatashin@soleen.com>,
Pratyush Yadav <pratyush@kernel.org>,
linux-kernel@vger.kernel.org, kexec@lists.infradead.org,
linux-mm@kvack.org, usamaarif642@gmail.com,
SeongJae Park <sj@kernel.org>,
kernel-team@meta.com
Subject: Re: [PATCH v7 4/6] kho: fix kho_in_debugfs_init() to handle non-FDT blobs
Date: Mon, 9 Mar 2026 10:22:50 +0200 [thread overview]
Message-ID: <aa6DWto0xY5EPyxK@kernel.org> (raw)
In-Reply-To: <20260306-kho-v7-4-404d14c188bb@debian.org>
On Fri, Mar 06, 2026 at 04:39:23AM -0800, Breno Leitao wrote:
> kho_in_debugfs_init() has two problems when displaying incoming
> sub-blobs in debugfs:
>
> 1. It uses the hardcoded property name "fdt" instead of
> KHO_FDT_SUB_TREE_PROP_NAME ("preserved-data"), so it never finds
> subtrees stored by the current kho_add_subtree().
>
> 2. It calls fdt_totalsize() to determine blob sizes, which assumes
> all blobs are FDTs. This breaks for non-FDT blobs like struct
> kho_kexec_metadata.
>
> Fix both issues by using KHO_FDT_SUB_TREE_PROP_NAME to find subtrees
> and reading the "blob-size" property from the FDT (persisted by
> kho_add_subtree()) instead of calling fdt_totalsize().
>
> Signed-off-by: Breno Leitao <leitao@debian.org>
> ---
> kernel/liveupdate/kexec_handover_debugfs.c | 38 ++++++++++++++++++++----------
> 1 file changed, 26 insertions(+), 12 deletions(-)
>
> diff --git a/kernel/liveupdate/kexec_handover_debugfs.c b/kernel/liveupdate/kexec_handover_debugfs.c
> index 7a100f2bf3947..fc2baa8b104fd 100644
> --- a/kernel/liveupdate/kexec_handover_debugfs.c
> +++ b/kernel/liveupdate/kexec_handover_debugfs.c
> @@ -13,6 +13,7 @@
> #include <linux/io.h>
> #include <linux/libfdt.h>
> #include <linux/mm.h>
> +#include <linux/kho/abi/kexec_handover.h>
> #include "kexec_handover_internal.h"
>
> static struct dentry *debugfs_root;
> @@ -121,23 +122,36 @@ __init void kho_in_debugfs_init(struct kho_debugfs *dbg, const void *fdt)
> fdt_for_each_subnode(child, fdt, 0) {
> int len = 0;
> const char *name = fdt_get_name(fdt, child, NULL);
> - const u64 *fdt_phys;
> - void *sub_fdt;
> -
> - fdt_phys = fdt_getprop(fdt, child, "fdt", &len);
> - if (!fdt_phys)
> + const u64 *blob_phys;
> + const u64 *blob_size;
> + void *blob;
> + size_t size;
Do we really need two size variables? Can't we just have u64 *size and pass
*size to __kho_debugfs_blob_add()?
> +
> + blob_phys = fdt_getprop(fdt, child,
> + KHO_FDT_SUB_TREE_PROP_NAME, &len);
> + if (!blob_phys)
> continue;
> - if (len != sizeof(*fdt_phys)) {
> - pr_warn("node %s prop fdt has invalid length: %d\n",
> - name, len);
> + if (len != sizeof(*blob_phys)) {
> + pr_warn("node %s prop %s has invalid length: %d\n",
> + name, KHO_FDT_SUB_TREE_PROP_NAME, len);
> continue;
> }
> - sub_fdt = phys_to_virt(*fdt_phys);
> +
> + blob_size = fdt_getprop(fdt, child,
> + KHO_FDT_SUB_TREE_SIZE_PROP_NAME, &len);
> + if (!blob_size || len != sizeof(*blob_size)) {
> + pr_warn("node %s missing or invalid %s property\n",
> + name, KHO_FDT_SUB_TREE_SIZE_PROP_NAME);
> + continue;
> + }
> + size = (size_t)*blob_size;
> +
> + blob = phys_to_virt(*blob_phys);
> err = __kho_debugfs_blob_add(&dbg->fdt_list, sub_fdt_dir, name,
> - sub_fdt, fdt_totalsize(sub_fdt));
> + blob, size);
> if (err) {
> - pr_warn("failed to add fdt %s to debugfs: %pe\n", name,
> - ERR_PTR(err));
> + pr_warn("failed to add blob %s to debugfs: %pe\n",
> + name, ERR_PTR(err));
> continue;
> }
> }
>
> --
> 2.47.3
>
>
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2026-03-09 8:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-06 12:39 [PATCH v7 0/6] kho: history: track previous kernel version and kexec boot count Breno Leitao
2026-03-06 12:39 ` [PATCH v7 1/6] kho: add size parameter to kho_add_subtree() Breno Leitao
2026-03-06 12:39 ` [PATCH v7 2/6] kho: rename fdt parameter to blob in kho_add/remove_subtree() Breno Leitao
2026-03-09 7:58 ` Mike Rapoport
2026-03-06 12:39 ` [PATCH v7 3/6] kho: persist blob size in KHO FDT Breno Leitao
2026-03-09 8:04 ` Mike Rapoport
2026-03-06 12:39 ` [PATCH v7 4/6] kho: fix kho_in_debugfs_init() to handle non-FDT blobs Breno Leitao
2026-03-09 8:22 ` Mike Rapoport [this message]
2026-03-09 13:01 ` Breno Leitao
2026-03-06 12:39 ` [PATCH v7 5/6] kho: kexec-metadata: track previous kernel chain Breno Leitao
2026-03-06 12:39 ` [PATCH v7 6/6] kho: document kexec-metadata tracking feature Breno Leitao
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=aa6DWto0xY5EPyxK@kernel.org \
--to=rppt@kernel.org \
--cc=graf@amazon.com \
--cc=kernel-team@meta.com \
--cc=kexec@lists.infradead.org \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pasha.tatashin@soleen.com \
--cc=pratyush@kernel.org \
--cc=sj@kernel.org \
--cc=usamaarif642@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.