From: Nikolay Borisov <nborisov@suse.com>
To: Qu Wenruo <wqu@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 1/3] btrfs-progs: Remove the dead branch in btrfs_run_delayed_refs()
Date: Tue, 16 Apr 2019 10:36:00 +0300 [thread overview]
Message-ID: <be947f9e-a552-7661-066a-4b469ff229e5@suse.com> (raw)
In-Reply-To: <20190416071526.3576-2-wqu@suse.com>
On 16.04.19 г. 10:15 ч., Qu Wenruo wrote:
> cleanup_ref_head() will only return 0 or 1, no way to return minutes
> value.
>
> So remove the dead branch.
>
> Signed-off-by: Qu Wenruo <wqu@suse.com>
This is a left-over from the kernel copy, due to the kernel version able
to return < 0 from, say, run_and_cleanup_extent_op.
Reviewed-by: Nikolay Borisov <nborisov@suse.com>
> ---
> extent-tree.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/extent-tree.c b/extent-tree.c
> index 8c9cdeff3b02..b7ece0ccc237 100644
> --- a/extent-tree.c
> +++ b/extent-tree.c
> @@ -4235,8 +4235,6 @@ int btrfs_run_delayed_refs(struct btrfs_trans_handle *trans, unsigned long nr)
> /* We dropped our lock, we need to loop. */
> ret = 0;
> continue;
> - } else if (ret) {
> - return ret;
> }
> locked_ref = NULL;
> continue;
>
next prev parent reply other threads:[~2019-04-16 7:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 7:15 [PATCH 0/3] btrfs-progs: Handle error properly in btrfs_commit_transaction() Qu Wenruo
2019-04-16 7:15 ` [PATCH 1/3] btrfs-progs: Remove the dead branch in btrfs_run_delayed_refs() Qu Wenruo
2019-04-16 7:36 ` Nikolay Borisov [this message]
2019-04-16 7:15 ` [PATCH 2/3] btrfs-progs: Refactor btrfs_finish_extent_commit() Qu Wenruo
2019-04-16 7:39 ` Nikolay Borisov
2019-04-16 7:15 ` [PATCH 3/3] btrfs-progs: Handle error properly in btrfs_commit_transaction() Qu Wenruo
2019-04-16 7:48 ` Nikolay Borisov
2019-05-13 13:55 ` [PATCH 0/3] " David Sterba
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=be947f9e-a552-7661-066a-4b469ff229e5@suse.com \
--to=nborisov@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=wqu@suse.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox