Btrfs: fix transaction leak during fsync call
authorFilipe Manana <fdmanana@gmail.com>
Thu, 29 May 2014 22:31:39 +0000 (23:31 +0100)
committerChris Mason <clm@fb.com>
Tue, 10 Jun 2014 00:21:06 +0000 (17:21 -0700)
If btrfs_log_dentry_safe() returns an error, we set ret to 1 and
fall through with the goal of committing the transaction. However,
in the case where the inode doesn't need a full sync, we would call
btrfs_wait_ordered_range() against the target range for our inode,
and if it returned an error, we would return without commiting or
ending the transaction.

Signed-off-by: Filipe David Borba Manana <fdmanana@gmail.com>
Signed-off-by: Chris Mason <clm@fb.com>

No differences found