All of lore.kernel.org
 help / color / mirror / Atom feed
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 14/24] kernel/locking/lockdep.c:6710:10: error: use of undeclared identifier 'stack_trace'
Date: Sat, 22 Aug 2026 07:13:21 +0800	[thread overview]
Message-ID: <202608220728.EPdgObe8-lkp@intel.com> (raw)

tree:   https://github.com/jimc/linux.git scratchpad-v10
head:   a23fc077806416450fbeb0a5a534fd995e465430
commit: 336938fcdc2d4cb4705b1ebcae351ef17abee91e [14/24] locking/lockdep: Route stack trace entries to static bootstrap scratchpad
config: powerpc-randconfig-002-20260822 (https://download.01.org/0day-ci/archive/20260822/202608220728.EPdgObe8-lkp@intel.com/config)
compiler: clang version 24.0.0git (https://github.com/llvm/llvm-project 935bfc708590c60147a79c7df145bb6e68b1d388)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260822/202608220728.EPdgObe8-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/202608220728.EPdgObe8-lkp@intel.com/

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:1139:20: warning: unused variable 'e' [-Wunused-variable]
    1139 |         struct lock_list *e;
         |                           ^
>> kernel/locking/lockdep.c:6710:10: error: use of undeclared identifier 'stack_trace'
    6710 |                 sizeof(stack_trace) - lockdep_trace_scratchpad.remaining,
         |                        ^~~~~~~~~~~
>> kernel/locking/lockdep.c:6710:25: error: use of undeclared identifier 'lockdep_trace_scratchpad'
    6710 |                 sizeof(stack_trace) - lockdep_trace_scratchpad.remaining,
         |                                       ^~~~~~~~~~~~~~~~~~~~~~~~
   kernel/locking/lockdep.c:6711:18: error: use of undeclared identifier 'BOOTSTRAP_STACK_TRACE_ENTRIES'
    6711 |                 (unsigned long)BOOTSTRAP_STACK_TRACE_ENTRIES);
         |                                ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   1 warning and 5 errors generated.


vim +/stack_trace +6710 kernel/locking/lockdep.c

  6704	
  6705	static int __init lockdep_boot_report(void)
  6706	{
  6707		pr_info("lockdep: %lu/%lu bootstrap entries, %zu/%lu bootstrap traces used before buddy init, scratchrec active\n",
  6708			min_t(unsigned long, nr_list_entries, BOOTSTRAP_LOCKDEP_ENTRIES),
  6709			BOOTSTRAP_LOCKDEP_ENTRIES,
> 6710			sizeof(stack_trace) - lockdep_trace_scratchpad.remaining,
  6711			(unsigned long)BOOTSTRAP_STACK_TRACE_ENTRIES);
  6712		return 0;
  6713	}
  6714	core_initcall(lockdep_boot_report);
  6715	

--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2026-08-21 23:14 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=202608220728.EPdgObe8-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.