From: kernel test robot <lkp@intel.com>
To: "Jim Cromie" <jim.cromie@gmail.com>,
"Łukasz Bartosik" <ukaszb@chromium.org>
Cc: <oe-kbuild-all@lists.linux.dev>
Subject: [jimc:scratchpad-v10 15/24] kernel/locking/lockdep.c:263:2: error: use of undeclared identifier 'SCRATCHREC_INIT'
Date: Sun, 23 Aug 2026 20:23:56 +0800 [thread overview]
Message-ID: <202608230325.neM6byLu-lkp@intel.com> (raw)
tree: https://github.com/jimc/linux.git scratchpad-v10
head: a23fc077806416450fbeb0a5a534fd995e465430
commit: 468ef4eda872252a66884b59339c1331ded8a0fc [15/24] locking/lockdep: Back lock_classes chunk array with dynamic scratchrec pool
config: x86_64-randconfig-001-20260822 (https://download.01.org/0day-ci/archive/20260823/202608230325.neM6byLu-lkp@intel.com/config)
compiler: clang version 22.1.3 (https://github.com/llvm/llvm-project e9846648fd6183ee6d8cbdb4502213fcf902a211)
rustc: rustc 1.96.0 (ac68faa20 2026-05-25)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260823/202608230325.neM6byLu-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/202608230325.neM6byLu-lkp@intel.com/
Note: the jimc/scratchpad-v10 HEAD a23fc077806416450fbeb0a5a534fd995e465430 builds fine.
It only hurts bisectability.
All errors (new ones prefixed by >>):
kernel/locking/lockdep.c:71:33: error: too many arguments provided to function-like macro invocation
71 | SCRATCH_64K_ORDER, 0, &lockdep_pool_key);
| ^
include/linux/scratchpad.h:360:9: note: macro 'SCRATCHREC_INIT_STATIC' defined here
360 | #define SCRATCHREC_INIT_STATIC(name, _elem_size, _static_buf, _size_bytes, _min_order, _key) \
| ^
kernel/locking/lockdep.c:69:2: error: use of undeclared identifier 'SCRATCHREC_INIT_STATIC'
69 | SCRATCHREC_INIT_STATIC(lockdep_pool, sizeof(struct lock_list),
| ^~~~~~~~~~~~~~~~~~~~~~
kernel/locking/lockdep.c:265:26: error: too many arguments provided to function-like macro invocation
265 | SCRATCH_64K_ORDER, 0, &lockdep_pool_key);
| ^
include/linux/scratchpad.h:357:9: note: macro 'SCRATCHREC_INIT' defined here
357 | #define SCRATCHREC_INIT(name, _elem_size, _min_order, _key) \
| ^
>> kernel/locking/lockdep.c:263:2: error: use of undeclared identifier 'SCRATCHREC_INIT'
263 | SCRATCHREC_INIT(lockdep_class_pool,
| ^~~~~~~~~~~~~~~
kernel/locking/lockdep.c:608:11: error: too many arguments provided to function-like macro invocation
608 | &lockdep_pool_key);
| ^
include/linux/scratchpad.h:153:9: note: macro 'SCRATCHPAD_INIT_STATIC' defined here
153 | #define SCRATCHPAD_INIT_STATIC(name, _static_buf, _size_bytes, _min_order, _key) \
| ^
kernel/locking/lockdep.c:605:2: error: use of undeclared identifier 'SCRATCHPAD_INIT_STATIC'
605 | SCRATCHPAD_INIT_STATIC(lockdep_trace_scratchpad,
| ^~~~~~~~~~~~~~~~~~~~~~
6 errors generated.
vim +/SCRATCHREC_INIT +263 kernel/locking/lockdep.c
261
262 static struct scratchrec lockdep_class_pool =
> 263 SCRATCHREC_INIT(lockdep_class_pool,
264 sizeof(struct lock_class) * LOCK_CLASSES_PER_CHUNK,
265 SCRATCH_64K_ORDER, 0, &lockdep_pool_key);
266
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-08-23 12:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202608230325.neM6byLu-lkp@intel.com \
--to=lkp@intel.com \
--cc=jim.cromie@gmail.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=ukaszb@chromium.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.