linux-kernel - Re: [PATCH] Btrfs: Refactor btrfs_lock

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <53A7FE82.3070303@cn.fujitsu.com>
Date:	Mon, 23 Jun 2014 18:16:34 +0800
From:	Miao Xie <miaox@...fujitsu.com>
To:	Geert Uytterhoeven <geert@...ux-m68k.org>,
	Chris Mason <clm@...com>, Josef Bacik <jbacik@...com>
CC:	<linux-btrfs@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] Btrfs: Refactor btrfs_lock_cluster() to kill compiler
 warning

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@...ux-m68k.org>

Looks good to me.

Reviewed-and-Tested-by: Miao Xie <miaox@...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
> 

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/