From: David Sterba <dsterba@suse.cz>
To: Anand Jain <anand.jain@oracle.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v3 1/6] btrfs: btrfs_cleanup_fs_roots handle ret variable
Date: Tue, 21 May 2024 17:10:50 +0200 [thread overview]
Message-ID: <20240521151050.GO17126@twin.jikos.cz> (raw)
In-Reply-To: <2a831fc01d65612914702b968174945f2f7e1c79.1715783315.git.anand.jain@oracle.com>
On Thu, May 16, 2024 at 07:12:10PM +0800, Anand Jain wrote:
> Since err represents the function return value, rename it as ret,
> and rename the original ret, which serves as a helper return value,
> to found. Also, optimize the code to continue call btrfs_put_root()
> for the rest of the root if even after btrfs_orphan_cleanup() returns
> error.
>
> Signed-off-by: Anand Jain <anand.jain@oracle.com>
> ---
> v3: Add a code comment.
> v2: Rename to 'found' instead of 'ret2' (Josef).
> Call btrfs_put_root() in the while-loop, avoids use of the variable
> 'found' outside of the while loop (Qu).
> Use 'unsigned int i' instead of 'int' (Goffredo).
>
> fs/btrfs/disk-io.c | 38 ++++++++++++++++++++------------------
> 1 file changed, 20 insertions(+), 18 deletions(-)
>
> diff --git a/fs/btrfs/disk-io.c b/fs/btrfs/disk-io.c
> index a91a8056758a..d38cf973b02a 100644
> --- a/fs/btrfs/disk-io.c
> +++ b/fs/btrfs/disk-io.c
> @@ -2925,22 +2925,23 @@ static int btrfs_cleanup_fs_roots(struct btrfs_fs_info *fs_info)
> {
> u64 root_objectid = 0;
> struct btrfs_root *gang[8];
> - int i = 0;
> - int err = 0;
> - unsigned int ret = 0;
> + int ret = 0;
>
> while (1) {
> + unsigned int i;
> + unsigned int found;
> +
> spin_lock(&fs_info->fs_roots_radix_lock);
> - ret = radix_tree_gang_lookup(&fs_info->fs_roots_radix,
> + found = radix_tree_gang_lookup(&fs_info->fs_roots_radix,
> (void **)gang, root_objectid,
> ARRAY_SIZE(gang));
> - if (!ret) {
> + if (!found) {
> spin_unlock(&fs_info->fs_roots_radix_lock);
> break;
> }
> - root_objectid = btrfs_root_id(gang[ret - 1]) + 1;
> + root_objectid = btrfs_root_id(gang[found - 1]) + 1;
>
> - for (i = 0; i < ret; i++) {
> + for (i = 0; i < found; i++) {
You could also move the declaration of 'i' to the for loop as you move
the other definition anyway.
> /* Avoid to grab roots in dead_roots. */
> if (btrfs_root_refs(&gang[i]->root_item) == 0) {
> gang[i] = NULL;
> @@ -2951,24 +2952,25 @@ static int btrfs_cleanup_fs_roots(struct btrfs_fs_info *fs_info)
> }
> spin_unlock(&fs_info->fs_roots_radix_lock);
>
> - for (i = 0; i < ret; i++) {
> + for (i = 0; i < found; i++) {
> if (!gang[i])
> continue;
> root_objectid = btrfs_root_id(gang[i]);
> - err = btrfs_orphan_cleanup(gang[i]);
> - if (err)
> - goto out;
> + /*
> + * Continue to release the remaining roots after the first
> + * error without cleanup and preserve the first error
> + * for the return.
> + */
> + if (!ret)
> + ret = btrfs_orphan_cleanup(gang[i]);
> btrfs_put_root(gang[i]);
> }
> + if (ret)
> + break;
> +
> root_objectid++;
> }
> -out:
> - /* Release the uncleaned roots due to error. */
> - for (; i < ret; i++) {
> - if (gang[i])
> - btrfs_put_root(gang[i]);
> - }
> - return err;
> + return ret;
> }
>
> /*
> --
> 2.38.1
>
next prev parent reply other threads:[~2024-05-21 15:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-16 11:12 [PATCH v3 0/6] part3 trivial adjustments for return variable coding style Anand Jain
2024-05-16 11:12 ` [PATCH v3 1/6] btrfs: btrfs_cleanup_fs_roots handle ret variable Anand Jain
2024-05-21 15:10 ` David Sterba [this message]
2024-05-21 17:08 ` Anand Jain
2024-05-16 11:12 ` [PATCH v3 2/6] btrfs: simplify ret in btrfs_recover_relocation Anand Jain
2024-05-16 11:12 ` [PATCH v3 3/6] btrfs: rename " Anand Jain
2024-05-16 11:12 ` [PATCH v3 4/6] btrfs: rename err " Anand Jain
2024-05-16 11:12 ` [PATCH v3 5/6] btrfs: btrfs_drop_snapshot optimize return variable Anand Jain
2024-05-16 11:12 ` [PATCH v3 6/6] btrfs: rename and optimize return variable in btrfs_find_orphan_roots Anand Jain
2024-05-21 15:18 ` David Sterba
2024-05-21 17:10 ` Anand Jain
2024-05-21 17:59 ` David Sterba
2024-05-23 14:35 ` Anand Jain
2024-05-21 1:04 ` [PATCH v3 0/6] part3 trivial adjustments for return variable coding style Anand Jain
2024-05-21 15:21 ` David Sterba
2024-05-21 17:10 ` Anand Jain
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=20240521151050.GO17126@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=anand.jain@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox