From: Miao Xie <miaox@cn.fujitsu.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
Chris Mason <clm@fb.com>, Josef Bacik <jbacik@fb.com>
Cc: <linux-btrfs@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Btrfs: Refactor btrfs_lock_cluster() to kill compiler warning
Date: Mon, 23 Jun 2014 18:16:34 +0800 [thread overview]
Message-ID: <53A7FE82.3070303@cn.fujitsu.com> (raw)
In-Reply-To: <1403440209-13370-1-git-send-email-geert@linux-m68k.org>
On Sun, 22 Jun 2014 14:30:09 +0200, Geert Uytterhoeven wrote:
> fs/btrfs/extent-tree.c: In function ‘btrfs_lock_cluster’:
> fs/btrfs/extent-tree.c:6399: warning: ‘used_bg’ may be used uninitialized in this function
>
> - Replace "again: ... goto again;" by standard C "while (1) { ... }",
> - Move block not processed during the first iteration of the loop to the
> end of the loop, which allows to kill the "locked" variable,
>
> Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
Looks good to me.
Reviewed-and-Tested-by: Miao Xie <miaox@cn.fujitsu.com>
> ---
> Please review, compile tested only.
> ---
> fs/btrfs/extent-tree.c | 42 ++++++++++++++++++++----------------------
> 1 file changed, 20 insertions(+), 22 deletions(-)
>
> diff --git a/fs/btrfs/extent-tree.c b/fs/btrfs/extent-tree.c
> index 99c253918208..e151c4a73d7b 100644
> --- a/fs/btrfs/extent-tree.c
> +++ b/fs/btrfs/extent-tree.c
> @@ -6397,36 +6397,34 @@ btrfs_lock_cluster(struct btrfs_block_group_cache *block_group,
> int delalloc)
> {
> struct btrfs_block_group_cache *used_bg;
> - bool locked = false;
> -again:
> +
> spin_lock(&cluster->refill_lock);
> - if (locked) {
> - if (used_bg == cluster->block_group)
> - return used_bg;
> + while (1) {
> + used_bg = cluster->block_group;
> + if (!used_bg)
> + return NULL;
>
> - up_read(&used_bg->data_rwsem);
> - btrfs_put_block_group(used_bg);
> - }
> + if (used_bg == block_group)
> + return used_bg;
>
> - used_bg = cluster->block_group;
> - if (!used_bg)
> - return NULL;
> + btrfs_get_block_group(used_bg);
>
> - if (used_bg == block_group)
> - return used_bg;
> + if (!delalloc)
> + return used_bg;
>
> - btrfs_get_block_group(used_bg);
> + if (down_read_trylock(&used_bg->data_rwsem))
> + return used_bg;
>
> - if (!delalloc)
> - return used_bg;
> + spin_unlock(&cluster->refill_lock);
> + down_read(&used_bg->data_rwsem);
>
> - if (down_read_trylock(&used_bg->data_rwsem))
> - return used_bg;
> + spin_lock(&cluster->refill_lock);
> + if (used_bg == cluster->block_group)
> + return used_bg;
>
> - spin_unlock(&cluster->refill_lock);
> - down_read(&used_bg->data_rwsem);
> - locked = true;
> - goto again;
> + up_read(&used_bg->data_rwsem);
> + btrfs_put_block_group(used_bg);
> + }
> }
>
> static inline void
>
prev parent reply other threads:[~2014-06-23 10:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-22 12:30 [PATCH] Btrfs: Refactor btrfs_lock_cluster() to kill compiler warning Geert Uytterhoeven
2014-06-23 10:16 ` Miao Xie [this message]
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=53A7FE82.3070303@cn.fujitsu.com \
--to=miaox@cn.fujitsu.com \
--cc=clm@fb.com \
--cc=geert@linux-m68k.org \
--cc=jbacik@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@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