From: Andrew Morton <akpm@linux-foundation.org>
To: Baoquan He <bhe@redhat.com>
Cc: "Bouron, Justinien" <jbouron@amazon.com>,
"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
Petr Mladek <pmladek@suse.com>,
Mario Limonciello <mario.limonciello@amd.com>,
Marcos Paulo de Souza <mpdesouza@suse.com>, "Graf (AWS),
Alexander" <graf@amazon.de>,
Steven Chen <chenste@linux.microsoft.com>,
Yan Zhao <yan.y.zhao@intel.com>,
"kexec@lists.infradead.org" <kexec@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Kudrjavets, Gunnar" <gunnarku@amazon.com>
Subject: Re: [PATCH] kexec_core: Remove superfluous page offset handling in segment loading
Date: Mon, 22 Sep 2025 20:07:32 -0700 [thread overview]
Message-ID: <20250922200732.f5c68c706e495635b1536ac2@linux-foundation.org> (raw)
In-Reply-To: <aMO5eKSpvwYAtDtX@MiWiFi-R3L-srv>
On Fri, 12 Sep 2025 14:11:04 +0800 Baoquan He <bhe@redhat.com> wrote:
> > int sanity_check_segment_list(struct kimage *image)
> > {
> > // ...
> > for (i = 0; i < nr_segments; i++) {
> > unsigned long mstart, mend;
> >
> > mstart = image->segment[i].mem;
> > mend = mstart + image->segment[i].memsz;
> > if (mstart > mend)
> > return -EADDRNOTAVAIL;
> > if ((mstart & ~PAGE_MASK) || (mend & ~PAGE_MASK))
> > return -EADDRNOTAVAIL;
> > if (mend >= KEXEC_DESTINATION_MEMORY_LIMIT)
> > return -EADDRNOTAVAIL;
> > }
> > // ...
> > }
> >
> > > That better be explained in log.
> > Does it warrant a second revision to change the log?
>
> I would appreciate it if we can tell the reason a little bit in patch
> log. Because we have codes as below where people assign a non PAGE_SIZE
> to kbuf.buf_align. With a general conclusion, people need explore code
> to find out. At least that's what I do when I check this patch.
>
> arch/x86/kernel/kexec-bzimage64.c:
> static void *bzImage64_load(struct kimage *image, char *kernel,
> unsigned long kernel_len, char *initrd,
> unsigned long initrd_len, char *cmdline,
> unsigned long cmdline_len)
> {
I'll drop this patch. Justinien, please send along an updated version
for the next -rc cycle, thanks.
next prev parent reply other threads:[~2025-09-23 3:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-10 16:31 Justinien Bouron
2025-09-11 9:41 ` Baoquan He
2025-09-11 15:30 ` Bouron, Justinien
2025-09-12 6:11 ` Baoquan He
2025-09-23 3:07 ` Andrew Morton [this message]
2025-09-11 13:24 ` kernel test robot
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=20250922200732.f5c68c706e495635b1536ac2@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=chenste@linux.microsoft.com \
--cc=graf@amazon.de \
--cc=gunnarku@amazon.com \
--cc=jbouron@amazon.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=mpdesouza@suse.com \
--cc=pmladek@suse.com \
--cc=rafael.j.wysocki@intel.com \
--cc=yan.y.zhao@intel.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
all inboxes | Powered by JetHome®