Btrfs: fix release reserved extents trace points
authorJosef Bacik <jbacik@fb.com>
Fri, 25 Mar 2016 17:25:58 +0000 (13:25 -0400)
committerDavid Sterba <dsterba@suse.com>
Thu, 7 Jul 2016 16:45:53 +0000 (18:45 +0200)
commit31bada7c4e5e80b9cc031e89247175bed58ed9e9
tree597f4768ea598716995e8640b521aa5ae19a0bba
parentdce3afa5932776f7b925249fbef435c265014f91
Btrfs: fix release reserved extents trace points

We were doing trace_btrfs_release_reserved_extent() in pin_down_extent which
isn't quite right because we will go through and free that extent later when we
unpin, so it messes up apps that are accounting for the reservation space.  We
were also unconditionally doing it in __btrfs_free_reserved_extent(), when we
only actually free the reservation instead of pinning the extent.  Thanks,

Signed-off-by: Josef Bacik <jbacik@fb.com>
Signed-off-by: David Sterba <dsterba@suse.com>
fs/btrfs/extent-tree.c