]> git.kernelconcepts.de Git - karo-tx-linux.git/commitdiff
btrfs: flush_space: treat return value of do_chunk_alloc properly
authorAlex Lyakas <alex@zadarastorage.com>
Sun, 6 Dec 2015 10:32:31 +0000 (12:32 +0200)
committerChris Mason <clm@fb.com>
Thu, 25 Aug 2016 10:58:18 +0000 (03:58 -0700)
do_chunk_alloc returns 1 when it succeeds to allocate a new chunk.
But flush_space will not convert this to 0, and will also return 1.
As a result, reserve_metadata_bytes will think that flush_space failed,
and may potentially return this value "1" to the caller (depends how
reserve_metadata_bytes was called). The caller will also treat this as an error.
For example, btrfs_block_rsv_refill does:

int ret = -ENOSPC;
...
ret = reserve_metadata_bytes(root, block_rsv, num_bytes, flush);
if (!ret) {
        block_rsv_add_bytes(block_rsv, num_bytes, 0);
        return 0;
}

return ret;

So it will return -ENOSPC.

Signed-off-by: Alex Lyakas <alex@zadarastorage.com>
Reviewed-by: Josef Bacik <jbacik@fb.com>
Reviewed-by: Liu Bo <bo.li.liu@oracle.com>
Signed-off-by: David Sterba <dsterba@suse.com>
Signed-off-by: Chris Mason <clm@fb.com>
fs/btrfs/extent-tree.c

index e962b0e25324858fb1d81750bb268407e1445ff7..d2cc16ff3e21df511ea7f3001e11a056a54f5ed9 100644 (file)
@@ -4882,7 +4882,7 @@ static int flush_space(struct btrfs_root *root,
                                     btrfs_get_alloc_profile(root, 0),
                                     CHUNK_ALLOC_NO_FORCE);
                btrfs_end_transaction(trans, root);
-               if (ret == -ENOSPC)
+               if (ret > 0 || ret == -ENOSPC)
                        ret = 0;
                break;
        case COMMIT_TRANS: