All of lore.kernel.org
 help / color / mirror / Atom feed
From: Liu Bo <bo.li.liu@oracle.com>
To: Alex Lyakas <alex@zadarastorage.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [RFC PATCH] btrfs: flush_space: treat return value of do_chunk_alloc properly
Date: Thu, 3 Dec 2015 10:14:29 -0800	[thread overview]
Message-ID: <20151203181428.GA19589@localhost.localdomain> (raw)
In-Reply-To: <CAOcd+r3DHGSu5017ha+m1E9bv2YD4v-LCMBxYywNA9BaLK-DQg@mail.gmail.com>

On Thu, Dec 03, 2015 at 06:51:03PM +0200, Alex Lyakas wrote:
> 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.

It will return 1 instead of -ENOSPC.

The patch looks good, I noticed this before, but I didn't manage to trigger a error for this, did you catch a error like that?

Thanks,

-liubo

> 
> diff --git a/fs/btrfs/extent-tree.c b/fs/btrfs/extent-tree.c
> index 4b89680..1ba3f0d 100644
> --- a/fs/btrfs/extent-tree.c
> +++ b/fs/btrfs/extent-tree.c
> @@ -4727,7 +4727,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:
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2015-12-03 18:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-03 16:51 [RFC PATCH] btrfs: flush_space: treat return value of do_chunk_alloc properly Alex Lyakas
2015-12-03 18:14 ` Liu Bo [this message]
2015-12-06 10:19   ` Alex Lyakas
2015-12-06 10:32     ` Alex Lyakas
2015-12-06 18:59       ` Liu Bo
2015-12-03 18:18 ` Josef Bacik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20151203181428.GA19589@localhost.localdomain \
    --to=bo.li.liu@oracle.com \
    --cc=alex@zadarastorage.com \
    --cc=linux-btrfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.