[jimc:folio-pool-v2-lockdep 18/21] kernel/locking/lockdep.c:3877:28: error: 'chain_hlocks' undeclared; did you mean 'free_chain_hlocks'?

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:   e77ee8289ea0755b0ee299348504d4568f942d71
commit: 4530a53e6265de5abb7f5566fdb3d4fe0a7199c5 [18/21] locking/lockdep: Migrate chain_hlocks array to 2-level dynamic folio chunks
config: powerpc-allmodconfig (https://download.01.org/0day-ci/archive/20260818/[email protected]/config)
compiler: powerpc64-linux-gcc (GCC) 16.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260818/[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]/

All errors (new ones prefixed by >>):

   In file included from kernel/locking/lockdep.c:84:
   kernel/locking/lockdep_internals.h: In function 'debug_class_ops_inc':
   kernel/locking/lockdep_internals.h:251:23: error: 'lock_classes' undeclared (first use in this function); did you mean 'lock_class'?
     251 |         idx = class - lock_classes;
         |                       ^~~~~~~~~~~~
         |                       lock_class
   kernel/locking/lockdep_internals.h:251:23: note: each undeclared identifier is reported only once for each function it appears in
   kernel/locking/lockdep_internals.h: In function 'debug_class_ops_read':
   kernel/locking/lockdep_internals.h:260:23: error: 'lock_classes' undeclared (first use in this function); did you mean 'lock_class'?
     260 |         idx = class - lock_classes;
         |                       ^~~~~~~~~~~~
         |                       lock_class
   kernel/locking/lockdep.c: In function 'print_chain_keys_chain':
>> kernel/locking/lockdep.c:3877:28: error: 'chain_hlocks' undeclared (first use in this function); did you mean 'free_chain_hlocks'?
    3877 |                 hlock_id = chain_hlocks[chain->base + i];
         |                            ^~~~~~~~~~~~
         |                            free_chain_hlocks
   In file included from include/linux/array_size.h:5,
                    from include/linux/string.h:6,
                    from arch/powerpc/include/asm/paca.h:16,
                    from arch/powerpc/include/asm/current.h:13,
                    from include/linux/mutex.h:14,
                    from kernel/locking/lockdep.c:30:
   kernel/locking/lockdep.c: In function 'check_no_collision':
   kernel/locking/lockdep.c:3935:41: error: 'chain_hlocks' undeclared (first use in this function); did you mean 'free_chain_hlocks'?
    3935 |                 if (DEBUG_LOCKS_WARN_ON(chain_hlocks[chain->base + j] != id)) {
         |                                         ^~~~~~~~~~~~
   include/linux/compiler.h:77:45: note: in definition of macro 'unlikely'
      77 | # define unlikely(x)    __builtin_expect(!!(x), 0)
         |                                             ^
   kernel/locking/lockdep.c:3935:21: note: in expansion of macro 'DEBUG_LOCKS_WARN_ON'
    3935 |                 if (DEBUG_LOCKS_WARN_ON(chain_hlocks[chain->base + j] != id)) {
         |                     ^~~~~~~~~~~~~~~~~~~
   kernel/locking/lockdep.c: At top level:
   kernel/locking/lockdep.c:1189:13: warning: 'in_any_zapped_class_list' defined but not used [-Wunused-function]
    1189 | static bool in_any_zapped_class_list(struct lock_class *class)
         |             ^~~~~~~~~~~~~~~~~~~~~~~~


vim +3877 kernel/locking/lockdep.c

39e2e173fb1f90 Alfredo Alvarez Fernandez 2016-03-30  3868  
39e2e173fb1f90 Alfredo Alvarez Fernandez 2016-03-30  3869  static void print_chain_keys_chain(struct lock_chain *chain)
39e2e173fb1f90 Alfredo Alvarez Fernandez 2016-03-30  3870  {
39e2e173fb1f90 Alfredo Alvarez Fernandez 2016-03-30  3871  	int i;
f6ec8829ac9d59 Yuyang Du                 2019-05-06  3872  	u64 chain_key = INITIAL_CHAIN_KEY;
f611e8cf98ec90 Boqun Feng                2020-08-07  3873  	u16 hlock_id;
39e2e173fb1f90 Alfredo Alvarez Fernandez 2016-03-30  3874  
39e2e173fb1f90 Alfredo Alvarez Fernandez 2016-03-30  3875  	printk("depth: %u\n", chain->depth);
39e2e173fb1f90 Alfredo Alvarez Fernandez 2016-03-30  3876  	for (i = 0; i < chain->depth; i++) {
f611e8cf98ec90 Boqun Feng                2020-08-07 @3877  		hlock_id = chain_hlocks[chain->base + i];
f611e8cf98ec90 Boqun Feng                2020-08-07  3878  		chain_key = print_chain_key_iteration(hlock_id, chain_key);
39e2e173fb1f90 Alfredo Alvarez Fernandez 2016-03-30  3879  
9e99b37a40c36a Jim Cromie                2026-08-17  3880  		print_lock_name(NULL, idx_to_lock_class(chain_hlock_class_idx(hlock_id)));
39e2e173fb1f90 Alfredo Alvarez Fernandez 2016-03-30  3881  		printk("\n");
39e2e173fb1f90 Alfredo Alvarez Fernandez 2016-03-30  3882  	}
39e2e173fb1f90 Alfredo Alvarez Fernandez 2016-03-30  3883  }
39e2e173fb1f90 Alfredo Alvarez Fernandez 2016-03-30  3884  

:::::: The code at line 3877 was first introduced by commit
:::::: f611e8cf98ec908b9c2c0da6064a660fc6022487 lockdep: Take read/write status in consideration when generate chainkey

:::::: TO: Boqun Feng <[email protected]>
:::::: CC: Peter Zijlstra <[email protected]>

--
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.