From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Nikolay Borisov <nborisov@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 2/2] btrfs: Use list_for_each_entry_safe in free_reloc_roots
Date: Fri, 21 Feb 2020 21:23:19 +0800 [thread overview]
Message-ID: <7d5e99e4-4122-bec5-6fb8-83a29fb6ce41@gmx.com> (raw)
In-Reply-To: <20200221131124.24105-2-nborisov@suse.com>
On 2020/2/21 下午9:11, Nikolay Borisov wrote:
> The function always works on a local copy of the reloc root list, which
> cannot be modified outside of it so using list_for_each_entry is fine.
> Additionally the macro handles empty lists so drop list_empty checks of
> callers. No semantic changes.
>
> Signed-off-by: Nikolay Borisov <nborisov@suse.com>
Reviewed-by: Qu Wenruo <wqu@suse.com>
Thanks,
Qu
> ---
> fs/btrfs/relocation.c | 16 +++++-----------
> 1 file changed, 5 insertions(+), 11 deletions(-)
>
> diff --git a/fs/btrfs/relocation.c b/fs/btrfs/relocation.c
> index e5cb64409f7c..f13b79adf6b0 100644
> --- a/fs/btrfs/relocation.c
> +++ b/fs/btrfs/relocation.c
> @@ -2523,13 +2523,10 @@ int prepare_to_merge(struct reloc_control *rc, int err)
> static noinline_for_stack
> void free_reloc_roots(struct list_head *list)
> {
> - struct btrfs_root *reloc_root;
> + struct btrfs_root *reloc_root, *tmp;
>
> - while (!list_empty(list)) {
> - reloc_root = list_entry(list->next, struct btrfs_root,
> - root_list);
> + list_for_each_entry_safe(reloc_root, tmp, list, root_list)
> __del_reloc_root(reloc_root);
> - }
> }
>
> static noinline_for_stack
> @@ -2588,15 +2585,13 @@ void merge_reloc_roots(struct reloc_control *rc)
> out:
> if (ret) {
> btrfs_handle_fs_error(fs_info, ret, NULL);
> - if (!list_empty(&reloc_roots))
> - free_reloc_roots(&reloc_roots);
> + free_reloc_roots(&reloc_roots);
>
> /* new reloc root may be added */
> mutex_lock(&fs_info->reloc_mutex);
> list_splice_init(&rc->reloc_roots, &reloc_roots);
> mutex_unlock(&fs_info->reloc_mutex);
> - if (!list_empty(&reloc_roots))
> - free_reloc_roots(&reloc_roots);
> + free_reloc_roots(&reloc_roots);
> }
>
> BUG_ON(!RB_EMPTY_ROOT(&rc->reloc_root_tree.rb_root));
> @@ -4689,8 +4684,7 @@ int btrfs_recover_relocation(struct btrfs_root *root)
> out_free:
> kfree(rc);
> out:
> - if (!list_empty(&reloc_roots))
> - free_reloc_roots(&reloc_roots);
> + free_reloc_roots(&reloc_roots);
>
> btrfs_free_path(path);
>
>
next prev parent reply other threads:[~2020-02-21 13:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-21 13:11 [PATCH 1/2] btrfs: Remove superflous lock acquisition in __del_reloc_root Nikolay Borisov
2020-02-21 13:11 ` [PATCH 2/2] btrfs: Use list_for_each_entry_safe in free_reloc_roots Nikolay Borisov
2020-02-21 13:17 ` [PATCH v2 " Nikolay Borisov
2020-02-21 13:23 ` Qu Wenruo [this message]
2020-04-10 16:33 ` [PATCH " David Sterba
2020-02-21 13:22 ` [PATCH 1/2] btrfs: Remove superflous lock acquisition in __del_reloc_root Qu Wenruo
2020-04-10 16:29 ` 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=7d5e99e4-4122-bec5-6fb8-83a29fb6ce41@gmx.com \
--to=quwenruo.btrfs@gmx.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