6d3b050efa
Removing or replacing an extent map requires holding a write lock on the extent map's tree. We currently do that everywhere, except in one of the self tests, where it's harmless since there's no concurrency. In order to catch possible races in the future, assert that we are holding a write lock on the extent map tree before removing or replacing an extent map in the tree, and update the self test to obtain a write lock before removing extent maps. Reviewed-by: Johannes Thumshirn <johannes.thumshirn@wdc.com> Signed-off-by: Filipe Manana <fdmanana@suse.com> Signed-off-by: David Sterba <dsterba@suse.com> |
||
|---|---|---|
| .. | ||
| btrfs-tests.c | ||
| btrfs-tests.h | ||
| extent-buffer-tests.c | ||
| extent-io-tests.c | ||
| extent-map-tests.c | ||
| free-space-tests.c | ||
| free-space-tree-tests.c | ||
| inode-tests.c | ||
| qgroup-tests.c | ||