Btrfs: fix freeing delayed ref head while still holding its mutex
authorJosef Bacik <jbacik@fusionio.com>
Wed, 30 Jan 2013 21:03:59 +0000 (16:03 -0500)
committerJosef Bacik <jbacik@fusionio.com>
Wed, 20 Feb 2013 17:59:27 +0000 (12:59 -0500)
commiteb12db690c7eb0f6593ba5792f5861409e88bc03
tree598ead6ef59b9e511ec5bfe94e8fdbe52db551bf
parent063d006fa06fbf73fab370921120380333a33e85
Btrfs: fix freeing delayed ref head while still holding its mutex

I hit this error when reproducing a bug that would end in a transaction
abort.  We take the delayed ref head's mutex to keep anybody from processing
it while we're destroying it, but we fail to drop the mutex before we carry
on and free the damned thing.  Fix this by doing the remove logic for the
head ourselves and unlock the mutex, that way we can avoid use after free's
or hung tasks waiting on that mutex to come back so they know the delayed
ref completed.  Thanks,

Signed-off-by: Josef Bacik <jbacik@fusionio.com>
fs/btrfs/disk-io.c