summaryrefslogtreecommitdiff
path: root/fs/btrfs/inode-item.c
diff options
context:
space:
mode:
authorJosef Bacik <josef@toxicpanda.com>2021-12-04 01:18:12 +0300
committerDavid Sterba <dsterba@suse.com>2022-01-07 16:18:24 +0300
commit5caa490ed8f07488e47378999bd4ad451bf8858b (patch)
treec65ac19b2c7fafac0d671813c95aa67cb4ad06ee /fs/btrfs/inode-item.c
parent462b728ea83fa85f1c0d2b79efb6187745444ce5 (diff)
downloadlinux-5caa490ed8f07488e47378999bd4ad451bf8858b.tar.xz
btrfs: control extent reference updates with a control flag for truncate
We've had weird bugs in the past where we forgot to adjust the truncate path to deal with the fact that we can be called by the tree log path. Instead of checking if our root is a LOG_ROOT use a flag on the btrfs_truncate_control to indicate that we don't want to do extent reference updates during this truncate. Reviewed-by: Filipe Manana <fdmanana@suse.com> 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 'fs/btrfs/inode-item.c')
-rw-r--r--fs/btrfs/inode-item.c3
1 files changed, 1 insertions, 2 deletions
diff --git a/fs/btrfs/inode-item.c b/fs/btrfs/inode-item.c
index 278d579f50bd..4c753415ab06 100644
--- a/fs/btrfs/inode-item.c
+++ b/fs/btrfs/inode-item.c
@@ -659,8 +659,7 @@ delete:
}
should_throttle = false;
- if (del_item && extent_start != 0 &&
- root->root_key.objectid != BTRFS_TREE_LOG_OBJECTID) {
+ if (del_item && extent_start != 0 && !control->skip_ref_updates) {
struct btrfs_ref ref = { 0 };
bytes_deleted += extent_num_bytes;