[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20260128111929.73a13cc2d51ef113a586993e@linux-foundation.org>
Date: Wed, 28 Jan 2026 11:19:29 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Baoquan He <bhe@...hat.com>
Cc: Li Chen <me@...ux.beauty>, Mimi Zohar <zohar@...ux.ibm.com>, Tushar
Sugandhi <tusharsu@...ux.microsoft.com>, Eric Biggers
<ebiggers@...nel.org>, Alexander Graf <graf@...zon.com>, Steven Chen
<chenste@...ux.microsoft.com>, Coiby Xu <coxu@...hat.com>, Sourabh Jain
<sourabhjain@...ux.ibm.com>, Philipp Rudo <prudo@...hat.com>, Ricardo
Ribalda <ribalda@...omium.org>, "Steven Rostedt (Google)"
<rostedt@...dmis.org>, Ross Zwisler <zwisler@...gle.com>,
kexec@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] kexec: derive purgatory entry from symbol
On Wed, 28 Jan 2026 17:26:10 +0800 Baoquan He <bhe@...hat.com> wrote:
> On 01/28/26 at 12:35pm, Li Chen wrote:
> > kexec_load_purgatory() derives image->start by locating e_entry inside an
> > SHF_EXECINSTR section. If the purgatory object contains multiple executable
> > sections with overlapping sh_addr, the entrypoint check can match more than
> > once and trigger a WARN.
> >
> > Derive the entry section from the purgatory_start symbol when present and
> > compute image->start from its final placement. Keep the existing e_entry
> > fallback for purgatories that do not expose the symbol.
> >
> > WARNING: kernel/kexec_file.c:1009 at kexec_load_purgatory+0x395/0x3c0, CPU#10: kexec/1784
> > Call Trace:
> > <TASK>
> > bzImage64_load+0x133/0xa00
> > __do_sys_kexec_file_load+0x2b3/0x5c0
> > do_syscall_64+0x81/0x610
> > entry_SYSCALL_64_after_hwframe+0x76/0x7e
> >
> > Fixes: 8652d44f466a ("kexec: support purgatories with .text.hot sections")
> > Signed-off-by: Li Chen <me@...ux.beauty>
>
> LGTM,
>
> Acked-by: Baoquan He <bhe@...hat.com>
Thanks.
> By the way, a warning need be 'Fixes' tag and back ported to stable
> kernel?
Yup. I added the cc:stable.
Powered by blists - more mailing lists