Btrfs: unlock everything properly in the error case for nocow
authorJosef Bacik <josef@redhat.com>
Thu, 31 May 2012 19:58:55 +0000 (15:58 -0400)
committerChris Mason <chris.mason@oracle.com>
Fri, 15 Jun 2012 01:29:15 +0000 (21:29 -0400)
I was getting hung on umount when a transaction was aborted because a range
of one of the free space inodes was still locked.  This is because the nocow
stuff doesn't unlock anything on error.  This fixed the problem and I
verified that is what was happening.  Thanks,

Signed-off-by: Josef Bacik <josef@redhat.com>

No differences found