From: Josef Bacik <josef@toxicpanda.com>
To: Nikolay Borisov <nborisov@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2] btrfs: Simplify setup_nodes_for_search
Date: Fri, 13 Nov 2020 13:25:07 -0500 [thread overview]
Message-ID: <5d09fb4c-e983-b165-032e-66531caf9f59@toxicpanda.com> (raw)
In-Reply-To: <20201113072940.479655-1-nborisov@suse.com>
On 11/13/20 2:29 AM, Nikolay Borisov wrote:
> The function is needlessly convoluted. Fix that by:
>
> * Removing redundant sret variable definition in both if arms.
>
> * Replace the again/done labels with direct return statements, the
> function is short enough and doesn't do anything special upon exit.
>
> * Remove BUG_ON on split_node returning a positive number - it can't
> happen as split_node returns either 0 or a negative error code.
>
> Signed-off-by: Nikolay Borisov <nborisov@suse.com>
> ---
>
> V2:
> - Initialize ret to 0 by default in case we don't hit any of the branch conditions
> and simply exit.
>
> fs/btrfs/ctree.c | 30 ++++++++----------------------
> 1 file changed, 8 insertions(+), 22 deletions(-)
>
> diff --git a/fs/btrfs/ctree.c b/fs/btrfs/ctree.c
> index 892b467347a3..5de33cd85cac 100644
> --- a/fs/btrfs/ctree.c
> +++ b/fs/btrfs/ctree.c
> @@ -2390,56 +2390,42 @@ setup_nodes_for_search(struct btrfs_trans_handle *trans,
> int *write_lock_level)
> {
> struct btrfs_fs_info *fs_info = root->fs_info;
> - int ret;
> + int ret = 0;
>
> if ((p->search_for_split || ins_len > 0) && btrfs_header_nritems(b) >=
> BTRFS_NODEPTRS_PER_BLOCK(fs_info) - 3) {
> - int sret;
>
> if (*write_lock_level < level + 1) {
> *write_lock_level = level + 1;
> btrfs_release_path(p);
> - goto again;
> + return -EAGAIN;
> }
>
> reada_for_balance(p, level);
> - sret = split_node(trans, root, p, level);
> + ret = split_node(trans, root, p, level);
>
> - BUG_ON(sret > 0);
> - if (sret) {
> - ret = sret;
> - goto done;
> - }
> b = p->nodes[level];
While you're cleaning up you could delete this line as well.
> } else if (ins_len < 0 && btrfs_header_nritems(b) <
> BTRFS_NODEPTRS_PER_BLOCK(fs_info) / 2) {
> - int sret;
>
> if (*write_lock_level < level + 1) {
> *write_lock_level = level + 1;
> btrfs_release_path(p);
> - goto again;
> + return -EAGAIN;
> }
>
> reada_for_balance(p, level);
> - sret = balance_level(trans, root, p, level);
> + ret = balance_level(trans, root, p, level);
> + if (ret)
> + return ret;
>
> - if (sret) {
> - ret = sret;
> - goto done;
> - }
> b = p->nodes[level];
> if (!b) {
> btrfs_release_path(p);
> - goto again;
> + return -EAGAIN;
> }
> BUG_ON(btrfs_header_nritems(b) == 1);
And change this to ASSERT(). Thanks,
Josef
next prev parent reply other threads:[~2020-11-13 18:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-13 7:29 [PATCH v2] btrfs: Simplify setup_nodes_for_search Nikolay Borisov
2020-11-13 18:25 ` Josef Bacik [this message]
2020-11-16 15:47 ` 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=5d09fb4c-e983-b165-032e-66531caf9f59@toxicpanda.com \
--to=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=nborisov@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