tree 534dba9dae10fa3b8cdc4111176b3ec7450e922b
parent 1eafa6c73791e4f312324ddad9cbcaf6a1b6052b
author Josef Bacik <jbacik@fusionio.com> 1359384320 -0500
committer Josef Bacik <jbacik@fusionio.com> 1360098543 -0500

Btrfs: do not merge logged extents if we've removed them from the tree

You can run into this problem where if somebody is fsyncing and writing out
the existing extents you will have removed the extent map from the em tree,
but it's still valid for the current fsync so we go ahead and write it.  The
problem is we unconditionally try to merge it back into the em tree, but if
we've removed it from the em tree that will cause use after free problems.
Fix this to only merge if we are still a part of the tree.  Thanks,

Signed-off-by: Josef Bacik <jbacik@fusionio.com>