summaryrefslogtreecommitdiffstats
path: root/fs/btrfs
diff options
context:
space:
mode:
authorJosef Bacik <jbacik@fusionio.com>2013-10-07 10:45:07 -0400
committerChris Mason <chris.mason@fusionio.com>2013-11-11 21:55:58 -0500
commiteb58bb371a04d3bbab44ec0c5672ce69487bac1e (patch)
tree634411eadc545246043dc016ca436119a35ca1fd /fs/btrfs
parent80d94fb3df2bf24a500f13181921736fa23b6c3d (diff)
downloadop-kernel-dev-eb58bb371a04d3bbab44ec0c5672ce69487bac1e.zip
op-kernel-dev-eb58bb371a04d3bbab44ec0c5672ce69487bac1e.tar.gz
Btrfs: do not free the dirty bytes from the trans block rsv on cleanup
The transactions should be cleaning up their reservations on failure, this just causes us to have warnings on unmount because we go negative by free'ing reservations that have already been free'ed. Thanks, Signed-off-by: Josef Bacik <jbacik@fusionio.com> Signed-off-by: Chris Mason <chris.mason@fusionio.com>
Diffstat (limited to 'fs/btrfs')
-rw-r--r--fs/btrfs/disk-io.c2
1 files changed, 0 insertions, 2 deletions
diff --git a/fs/btrfs/disk-io.c b/fs/btrfs/disk-io.c
index d205bdd..fdc75ab 100644
--- a/fs/btrfs/disk-io.c
+++ b/fs/btrfs/disk-io.c
@@ -4046,8 +4046,6 @@ void btrfs_cleanup_one_transaction(struct btrfs_transaction *cur_trans,
btrfs_destroy_ordered_operations(cur_trans, root);
btrfs_destroy_delayed_refs(cur_trans, root);
- btrfs_block_rsv_release(root, &root->fs_info->trans_block_rsv,
- cur_trans->dirty_pages.dirty_bytes);
cur_trans->state = TRANS_STATE_COMMIT_START;
wake_up(&root->fs_info->transaction_blocked_wait);
OpenPOWER on IntegriCloud