btrfs: introduce BTRFS_NESTING_LEFT/BTRFS_NESTING_RIGHT
Our lockdep maps are based on rootid+level, however in some cases we will lock adjacent blocks on the same level, namely in searching forward or in split/balance. Because of this lockdep will complain, so we need a separate subclass to indicate to lockdep that these are different locks. lock leaf -> BTRFS_NESTING_NORMAL cow leaf -> BTRFS_NESTING_COW split leaf lock left -> BTRFS_NESTING_LEFT lock right -> BTRFS_NESTING_RIGHT The above graph illustrates the need for this new nesting subclass. Signed-off-by: Josef Bacik <josef@toxicpanda.com> Reviewed-by: David Sterba <dsterba@suse.com> Signed-off-by: David Sterba <dsterba@suse.com>
This commit is contained in:

committed by
David Sterba

parent
9631e4cc1a
commit
bf77467a93
@@ -32,6 +32,18 @@ enum btrfs_lock_nesting {
|
||||
*/
|
||||
BTRFS_NESTING_COW,
|
||||
|
||||
/*
|
||||
* Oftentimes we need to lock adjacent nodes on the same level while
|
||||
* still holding the lock on the original node we searched to, such as
|
||||
* for searching forward or for split/balance.
|
||||
*
|
||||
* Because of this we need to indicate to lockdep that this is
|
||||
* acceptable by having a different subclass for each of these
|
||||
* operations.
|
||||
*/
|
||||
BTRFS_NESTING_LEFT,
|
||||
BTRFS_NESTING_RIGHT,
|
||||
|
||||
/*
|
||||
* We are limited to MAX_LOCKDEP_SUBLCLASSES number of subclasses, so
|
||||
* add this in here and add a static_assert to keep us from going over
|
||||
|
Reference in New Issue
Block a user