diff options
| author | Josef Bacik <josef@toxicpanda.com> | 2020-08-20 18:46:07 +0300 |
|---|---|---|
| committer | David Sterba <dsterba@suse.com> | 2020-10-07 13:12:17 +0300 |
| commit | cf6f34aa3ada0be8c5f90fe93f48a75fea082c51 (patch) | |
| tree | eda9486b7532bda46f13e685536609de03b22592 /tools/perf/scripts/python/export-to-sqlite.py | |
| parent | 4dff97e69005ea90266f3e3dda295264e854c15d (diff) | |
| download | linux-cf6f34aa3ada0be8c5f90fe93f48a75fea082c51.tar.xz | |
btrfs: introduce BTRFS_NESTING_NEW_ROOT for adding new roots
The way we add new roots is confusing from a locking perspective for
lockdep. We generally have the rule that we lock things in order from
highest level to lowest, but in the case of adding a new level to the
tree we actually allocate a new block for the root, which makes the
locking go in reverse. A similar issue exists for snapshotting, we cow
the original root for the root of a new tree, however they're at the
same level. Address this by using BTRFS_NESTING_NEW_ROOT for these
operations.
Signed-off-by: Josef Bacik <josef@toxicpanda.com>
Reviewed-by: David Sterba <dsterba@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-sqlite.py')
0 files changed, 0 insertions, 0 deletions
