Btrfs: release both paths before logging dir/changed extents
authorJosef Bacik <jbacik@fusionio.com>
Mon, 22 Jul 2013 16:54:30 +0000 (12:54 -0400)
committerChris Mason <chris.mason@fusionio.com>
Fri, 9 Aug 2013 23:30:16 +0000 (19:30 -0400)
commitf3b15ccdbb9a79781578249a63318805e55a6c34
tree06a1fa7f70424dcbb111e7f68efe59950d93d86e
parentee20a98314e52a6675e94d1a07ca205ffdf09a72
Btrfs: release both paths before logging dir/changed extents

The ceph guys tripped over this bug where we were still holding onto the
original path that we used to copy the inode with when logging.  This is based
on Chris's fix which was reported to fix the problem.  We need to drop the paths
in two cases anyway so just move the drop up so that we don't have duplicate
code.  Thanks,

Cc: stable@vger.kernel.org
Signed-off-by: Josef Bacik <jbacik@fusionio.com>
Signed-off-by: Chris Mason <chris.mason@fusionio.com>
fs/btrfs/tree-log.c