From: kernel test robot <lkp@intel.com>
To: Mike Rapoport <rppt@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 4972/5926] kernel/kexec_handover_debug.c:16:18: error: use of undeclared identifier 'kho_scratch_cnt'
Date: Tue, 4 Nov 2025 22:48:31 +0800 [thread overview]
Message-ID: <202511042251.paO6f5BZ-lkp@intel.com> (raw)
Hi Mike,
First bad commit (maybe != root cause):
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 17490bd0527f59d841168457b245581f314b5fa0
commit: 8c211175c3abcebb8bffce8095d78d193e482105 [4972/5926] liveupdate-kho-warn-and-fail-on-metadata-or-preserved-memory-in-scratch-area-fix
config: x86_64-randconfig-071-20251104 (https://download.01.org/0day-ci/archive/20251104/202511042251.paO6f5BZ-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251104/202511042251.paO6f5BZ-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202511042251.paO6f5BZ-lkp@intel.com/
All errors (new ones prefixed by >>):
>> kernel/kexec_handover_debug.c:16:18: error: use of undeclared identifier 'kho_scratch_cnt'
16 | for (i = 0; i < kho_scratch_cnt; i++) {
| ^
>> kernel/kexec_handover_debug.c:17:19: error: use of undeclared identifier 'kho_scratch'
17 | scratch_start = kho_scratch[i].addr;
| ^
kernel/kexec_handover_debug.c:18:17: error: use of undeclared identifier 'kho_scratch'
18 | scratch_end = kho_scratch[i].addr + kho_scratch[i].size;
| ^
kernel/kexec_handover_debug.c:18:39: error: use of undeclared identifier 'kho_scratch'
18 | scratch_end = kho_scratch[i].addr + kho_scratch[i].size;
| ^
4 errors generated.
vim +/kho_scratch_cnt +16 kernel/kexec_handover_debug.c
4039a00022d42a Pasha Tatashin 2025-10-20 10
4039a00022d42a Pasha Tatashin 2025-10-20 11 bool kho_scratch_overlap(phys_addr_t phys, size_t size)
4039a00022d42a Pasha Tatashin 2025-10-20 12 {
4039a00022d42a Pasha Tatashin 2025-10-20 13 phys_addr_t scratch_start, scratch_end;
4039a00022d42a Pasha Tatashin 2025-10-20 14 unsigned int i;
4039a00022d42a Pasha Tatashin 2025-10-20 15
4039a00022d42a Pasha Tatashin 2025-10-20 @16 for (i = 0; i < kho_scratch_cnt; i++) {
4039a00022d42a Pasha Tatashin 2025-10-20 @17 scratch_start = kho_scratch[i].addr;
:::::: The code at line 16 was first introduced by commit
:::::: 4039a00022d42ac3d68b2eea63066bc9f7ef89ce kho: warn and fail on metadata or preserved memory in scratch area
:::::: TO: Pasha Tatashin <pasha.tatashin@soleen.com>
:::::: CC: Andrew Morton <akpm@linux-foundation.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2025-11-04 14:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 14:48 kernel test robot [this message]
2025-11-04 15:38 ` Mike Rapoport
2025-11-04 17:32 ` Pasha Tatashin
2025-11-04 17:50 ` Pasha Tatashin
2025-11-04 22:15 ` Andrew Morton
2025-11-04 23:12 ` Pasha Tatashin
2025-11-04 23:54 ` Andrew Morton
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=202511042251.paO6f5BZ-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rppt@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