From: Ronald Warsow <rwarsow@gmx.de>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>, stable@vger.kernel.org
Cc: patches@lists.linux.dev, linux-kernel@vger.kernel.org,
torvalds@linux-foundation.org, akpm@linux-foundation.org,
linux@roeck-us.net, shuah@kernel.org, patches@kernelci.org,
lkft-triage@lists.linaro.org, pavel@denx.de,
jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, conor@kernel.org,
hargar@microsoft.com, broonie@kernel.org, achill@achill.org,
sr@sladewatkins.com
Subject: Re: [PATCH 6.17 000/247] 6.17.9-rc1 review
Date: Fri, 21 Nov 2025 15:30:32 +0100 [thread overview]
Message-ID: <c982e824-3924-4fc0-aea8-9f940bb5f5b9@gmx.de> (raw)
In-Reply-To: <20251121130154.587656062@linuxfoundation.org>
Hi
with CONFIG_KEXEC_HANDOVER=n
no regressions here on x86_64 (RKL, Intel 11th Gen. CPU)
but with CONFIG_KEXEC_HANDOVER=y
the compiler runs in an error:
...
from kernel/kexec_handover.c:12:
kernel/kexec_handover.c: In function ‘kho_preserve_phys’:
kernel/kexec_handover.c:732:41: error: ‘nr_pages’ undeclared (first use
in this function); did you mean ‘dir_pages’?
732 | nr_pages << PAGE_SHIFT))) {
| ^~~~~~~~
./include/asm-generic/bug.h:123:32: note: in definition of macro ‘WARN_ON’
123 | int __ret_warn_on = !!(condition);
\
| ^~~~~~~~~
kernel/kexec_handover.c:732:41: note: each undeclared identifier is
reported only once for each function it appears in
732 | nr_pages << PAGE_SHIFT))) {
| ^~~~~~~~
./include/asm-generic/bug.h:123:32: note: in definition of macro ‘WARN_ON’
123 | int __ret_warn_on = !!(condition);
\
| ^~~~~~~~~
make[3]: *** [scripts/Makefile.build:287: kernel/kexec_handover.o] Error 1
...
===
I guess one of the four kho:* patches contains the bug
anyway
Thanks
Tested-by: Ronald Warsow <rwarsow@gmx.de>
next prev parent reply other threads:[~2025-11-21 14:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-21 13:09 Greg Kroah-Hartman
2025-11-21 14:30 ` Ronald Warsow [this message]
2025-11-21 15:25 ` Greg Kroah-Hartman
2025-11-21 16:28 ` Jon Hunter
2025-11-21 17:05 ` Jeffrin Thalakkottoor
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=c982e824-3924-4fc0-aea8-9f940bb5f5b9@gmx.de \
--to=rwarsow@gmx.de \
--cc=achill@achill.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hargar@microsoft.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@denx.de \
--cc=shuah@kernel.org \
--cc=sr@sladewatkins.com \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®