Btrfs: fixup reserved trace points
authorJosef Bacik <jbacik@fusionio.com>
Mon, 7 Oct 2013 19:18:52 +0000 (15:18 -0400)
committerChris Mason <chris.mason@fusionio.com>
Tue, 12 Nov 2013 02:56:31 +0000 (21:56 -0500)
commit0be5dc67c445230b0889dba63defba9a9e5561b4
tree0265e91c3b07d10e75a95627295680e1c733c355
parent2b1360da35877cd969ed83884d8989ba778254d0
Btrfs: fixup reserved trace points

In trying to track down where we were leaking reserved space I noticed our
reserve extent tracepoints are a little off.  First we were saying that the
reserved space had been alloced in btrfs_reserve_extent, which isn't the case,
this needs to be triggered when we actually allocate the space when we run the
delayed ref.  We were also missing a few places where we should have been
tracing the btrfs_reserve_extent_free tracepoint.  With these in place I was
able to put together where we were leaking reserved space.  Thanks,

Signed-off-by: Josef Bacik <jbacik@fusionio.com>
Signed-off-by: Chris Mason <chris.mason@fusionio.com>
fs/btrfs/extent-tree.c