Re: [PATCH] locking/ww_mutex: Adjust to lockdep nest_lock requirements

2023-12-22 Thread kernel test robot
Hello, kernel test robot noticed "WARNING:at_kernel/locking/lockdep.c:#__lock_acquire" on: commit: 4f37585fa02f3eaebc72efa1260e6742478c00fa ("[PATCH] locking/ww_mutex: Adjust to lockdep nest_lock requirements") url: https://github.com/intel-lab-lkp/linux/commits/Thom

[PATCH] locking/ww_mutex: Adjust to lockdep nest_lock requirements

2023-12-19 Thread Thomas Hellström
When using mutex_acquire_nest() with a nest_lock, lockdep refcounts the number of acquired lockdep_maps of mutexes of the same class, and also keeps a pointer to the first acquired lockdep_map of a class. That pointer is then used for various comparison-, printing- and checking purposes, but there

Re: [RFC PATCH] locking/ww_mutex: Adjust to lockdep nest_lock requirements

2023-09-11 Thread kernel test robot
Hello, kernel test robot noticed "WARNING:possible_recursive_locking_detected" on: commit: bb043828b2d487832c946751ffcc4ebd80d2a624 ("[RFC PATCH] locking/ww_mutex: Adjust to lockdep nest_lock requirements") url: https://github.com/intel-lab-lkp/linux/commits/Thom

[RFC PATCH] locking/ww_mutex: Adjust to lockdep nest_lock requirements

2023-09-11 Thread Thomas Hellström
When using mutex_acquire_nest() with a nest_lock, lockdep refcounts the number of acquired lockdep_maps of mutexes of the same class, and also keeps a pointer to the first acquired lockdep_map of a class. That pointer is then used for various comparison-, printing- and checking purposes, but there