diff options
| author | Filipe Manana <fdmanana@suse.com> | 2022-09-19 15:06:36 +0100 |
|---|---|---|
| committer | David Sterba <dsterba@suse.com> | 2022-09-29 17:08:31 +0200 |
| commit | 74333c7d87914ef1c250d3ea9441e88e15039bd8 (patch) | |
| tree | d93c0d5161d699c7f62bb3f033ed5b75464c4ce4 /fs/btrfs | |
| parent | 2e0cdaa0288bbe3d6a05937bc7b61aa9da0cb2bf (diff) | |
btrfs: assert tree is locked when clearing extent map from logging
When calling clear_em_logging() we should have a write lock on the extent
map tree, as we will try to merge the extent map with the previous and
next ones in the tree. So assert that we have a write lock.
Signed-off-by: Filipe Manana <fdmanana@suse.com>
Reviewed-by: David Sterba <dsterba@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'fs/btrfs')
| -rw-r--r-- | fs/btrfs/extent_map.c | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/fs/btrfs/extent_map.c b/fs/btrfs/extent_map.c index 6b7eee92d981..f1616aa8d0f5 100644 --- a/fs/btrfs/extent_map.c +++ b/fs/btrfs/extent_map.c @@ -334,6 +334,8 @@ out: void clear_em_logging(struct extent_map_tree *tree, struct extent_map *em) { + lockdep_assert_held_write(&tree->lock); + clear_bit(EXTENT_FLAG_LOGGING, &em->flags); if (extent_map_in_tree(em)) try_merge_map(tree, em); |