From: Pratyush Yadav <pratyush@kernel.org>
To: ranxiaokai627@163.com
Cc: graf@amazon.com, rppt@kernel.org, pasha.tatashin@soleen.com,
pratyush@kernel.org, akpm@linux-foundation.org,
kexec@lists.infradead.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, ran.xiaokai@zte.com.cn,
stable@vger.kernel.org
Subject: Re: [PATCH -next 1/2] kho: fix missing early_memunmap() call in kho_populate()
Date: Tue, 10 Feb 2026 14:45:02 +0100 [thread overview]
Message-ID: <2vxzv7g4sof5.fsf@kernel.org> (raw)
In-Reply-To: <20260206043121.197564-2-ranxiaokai627@163.com> (ranxiaokai's message of "Fri, 6 Feb 2026 04:31:20 +0000")
Hi Ran,
Thanks for the fix.
On Fri, Feb 06 2026, ranxiaokai627@163.com wrote:
> From: Ran Xiaokai <ran.xiaokai@zte.com.cn>
>
> kho_populate() returns without calling early_memunmap() on success
> path, this will cause early ioremap virtual address space leak.
>
> Fixes: b50634c5e84a ("kho: cleanup error handling in kho_populate()")
> Signed-off-by: Ran Xiaokai <ran.xiaokai@zte.com.cn>
> ---
>
> b50634c5e84a ("kho: cleanup error handling in kho_populate()")
> has not landed in upstream, so
> Cc: <stable@vger.kernel.org> is unnecessary?
>
> kernel/liveupdate/kexec_handover.c | 8 +++++---
> 1 file changed, 5 insertions(+), 3 deletions(-)
>
> diff --git a/kernel/liveupdate/kexec_handover.c b/kernel/liveupdate/kexec_handover.c
> index fb3a7b67676e..76b714db175d 100644
> --- a/kernel/liveupdate/kexec_handover.c
> +++ b/kernel/liveupdate/kexec_handover.c
> @@ -1463,6 +1463,7 @@ void __init kho_populate(phys_addr_t fdt_phys, u64 fdt_len,
> struct kho_scratch *scratch = NULL;
> phys_addr_t mem_map_phys;
> void *fdt = NULL;
> + int populated = 0;
Nit: Please use a bool and true/false. I think it reads much nicer.
> int err;
>
> /* Validate the input FDT */
> @@ -1529,16 +1530,17 @@ void __init kho_populate(phys_addr_t fdt_phys, u64 fdt_len,
> kho_in.scratch_phys = scratch_phys;
> kho_in.mem_map_phys = mem_map_phys;
> kho_scratch_cnt = scratch_cnt;
> - pr_info("found kexec handover data.\n");
>
> - return;
> + populated = 1;
> + pr_info("found kexec handover data.\n");
>
> err_unmap_scratch:
> early_memunmap(scratch, scratch_len);
> err_unmap_fdt:
> early_memunmap(fdt, fdt_len);
> err_report:
Nit: now that this code can be reached by non-error paths, we should
re-name the labels. I think dropping the "err_" prefix should be enough.
With these fixed,
Reviewed-by: Pratyush Yadav <pratyush@kernel.org>
> - pr_warn("disabling KHO revival\n");
> + if (!populated)
> + pr_warn("disabling KHO revival\n");
> }
>
> /* Helper functions for kexec_file_load */
--
Regards,
Pratyush Yadav
next prev parent reply other threads:[~2026-02-10 13:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-06 4:31 [PATCH -next 0/2] two fixes " ranxiaokai627
2026-02-06 4:31 ` [PATCH -next 1/2] kho: fix missing early_memunmap() call " ranxiaokai627
2026-02-10 13:45 ` Pratyush Yadav [this message]
2026-02-11 1:23 ` ranxiaokai627
2026-02-06 4:31 ` [PATCH -next 2/2] kho: remove unnecessary WARN_ON(err) " ranxiaokai627
2026-02-07 17:34 ` Pasha Tatashin
2026-02-10 13:45 ` Pratyush Yadav
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=2vxzv7g4sof5.fsf@kernel.org \
--to=pratyush@kernel.org \
--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=ran.xiaokai@zte.com.cn \
--cc=ranxiaokai627@163.com \
--cc=rppt@kernel.org \
--cc=stable@vger.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