diff options
| author | Jeff Mahoney <jeffm@suse.com> | 2016-06-08 00:36:38 -0400 |
|---|---|---|
| committer | Sasha Levin <sasha.levin@oracle.com> | 2016-07-12 08:46:54 -0400 |
| commit | eefeb9a25bfeb73a64fb92c3b7189d34b557dfe0 (patch) | |
| tree | e603d126c5b240967291e219e9193122aa7b6fc5 /fs/btrfs/ctree.c | |
| parent | bc4b57be51fa419cd870398624c763b7afb91154 (diff) | |
| download | linux-stable-eefeb9a25bfeb73a64fb92c3b7189d34b557dfe0.tar.gz linux-stable-eefeb9a25bfeb73a64fb92c3b7189d34b557dfe0.tar.bz2 linux-stable-eefeb9a25bfeb73a64fb92c3b7189d34b557dfe0.zip | |
btrfs: account for non-CoW'd blocks in btrfs_abort_transaction
[ Upstream commit 64c12921e11b3a0c10d088606e328c58e29274d8 ]
The test for !trans->blocks_used in btrfs_abort_transaction is
insufficient to determine whether it's safe to drop the transaction
handle on the floor. btrfs_cow_block, informed by should_cow_block,
can return blocks that have already been CoW'd in the current
transaction. trans->blocks_used is only incremented for new block
allocations. If an operation overlaps the blocks in the current
transaction entirely and must abort the transaction, we'll happily
let it clean up the trans handle even though it may have modified
the blocks and will commit an incomplete operation.
In the long-term, I'd like to do closer tracking of when the fs
is actually modified so we can still recover as gracefully as possible,
but that approach will need some discussion. In the short term,
since this is the only code using trans->blocks_used, let's just
switch it to a bool indicating whether any blocks were used and set
it when should_cow_block returns false.
Cc: stable@vger.kernel.org # 3.4+
Signed-off-by: Jeff Mahoney <jeffm@suse.com>
Reviewed-by: Filipe Manana <fdmanana@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>
Signed-off-by: Sasha Levin <sasha.levin@oracle.com>
Diffstat (limited to 'fs/btrfs/ctree.c')
| -rw-r--r-- | fs/btrfs/ctree.c | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/fs/btrfs/ctree.c b/fs/btrfs/ctree.c index f54511dd287e..39c68ef10808 100644 --- a/fs/btrfs/ctree.c +++ b/fs/btrfs/ctree.c @@ -1542,6 +1542,7 @@ noinline int btrfs_cow_block(struct btrfs_trans_handle *trans, trans->transid, root->fs_info->generation); if (!should_cow_block(trans, root, buf)) { + trans->dirty = true; *cow_ret = buf; return 0; } @@ -2762,8 +2763,10 @@ again: * then we don't want to set the path blocking, * so we test it here */ - if (!should_cow_block(trans, root, b)) + if (!should_cow_block(trans, root, b)) { + trans->dirty = true; goto cow_done; + } /* * must have write locks on this node and the |