[jimc:folio-pool-v2-lockdep 14/21] kernel/locking/lockdep.c:587:1: sparse: sparse: symbol 'lockdep_trace_scratchpad_key' was not declared. Should it be static?

kernel test robot <[email protected]>
Newsgroups dev.linux.lists.oe-kbuild-all
Message-ID <[email protected]>
tree:   https://github.com/jimc/linux.git folio-pool-v2-lockdep
head:   b6042163d72458308afa7eef95a3293507a1538e
commit: 198cb0234063750d4125d2f5b3fd29f373fba200 [14/21] locking/lockdep: Migrate and compact stack trace entries into folio_scratchpad
config: x86_64-randconfig-122-20260819 (https://download.01.org/0day-ci/archive/20260819/[email protected]/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260819/[email protected]/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 <[email protected]>
| Closes: https://lore.kernel.org/oe-kbuild-all/[email protected]/

sparse warnings: (new ones prefixed by >>)
   kernel/locking/lockdep.c:63:1: sparse: sparse: symbol 'lockdep_pool_key' was not declared. Should it be static?
>> kernel/locking/lockdep.c:587:1: sparse: sparse: symbol 'lockdep_trace_scratchpad_key' was not declared. Should it be static?
   kernel/locking/lockdep.c:3517:49: sparse: sparse: cast truncates bits from constant value (50000 becomes 0)
   kernel/locking/lockdep.c:3517:49: sparse: sparse: cast truncates bits from constant value (50000 becomes 0)

vim +/lockdep_trace_scratchpad_key +587 kernel/locking/lockdep.c

   586	
 > 587	DEFINE_STATIC_KEY_TRUE(lockdep_trace_scratchpad_key);
   588	static struct folio_scratchpad lockdep_trace_scratchpad =
   589		FOLIO_SCRATCHPAD_INIT_KEY(lockdep_trace_scratchpad,
   590					  FOLIO_POOL_64K_ORDER,
   591					  &lockdep_trace_scratchpad_key);
   592	

--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.