linux-kernel - Re: [PATCH] ext4: remove unneeded variable.

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <4EC80D6E.3090404@linux.vnet.ibm.com>
Date:	Sun, 20 Nov 2011 01:41:26 +0530
From:	"Srivatsa S. Bhat" <srivatsa.bhat@...ux.vnet.ibm.com>
To:	Namjae Jeon <linkinjeon@...il.com>
CC:	tytso@....edu, linux-kernel@...r.kernel.org,
	linux-ext4@...r.kernel.org,
	Amit Sahrawat <amit.sahrawat83@...il.com>
Subject: Re: [PATCH] ext4: remove unneeded variable.

On 11/11/2011 08:32 PM, Namjae Jeon wrote:
> ret2 is not needed in ext4_flush_completed_IO().
> 

Not needed? I went through the code briefly, and I don't agree.

> Signed-off-by: Namjae Jeon <linkinjeon@...il.com>
> Signed-off-by: Amit Sahrawat <amit.sahrawat83@...il.com>
> ---
>  fs/ext4/fsync.c |    5 +----
>  1 files changed, 1 insertions(+), 4 deletions(-)
> 
> diff --git a/fs/ext4/fsync.c b/fs/ext4/fsync.c
> index 00a2cb7..40397ac 100644
> --- a/fs/ext4/fsync.c
> +++ b/fs/ext4/fsync.c
> @@ -81,7 +81,6 @@ int ext4_flush_completed_IO(struct inode *inode)
>  	struct ext4_inode_info *ei = EXT4_I(inode);
>  	unsigned long flags;
>  	int ret = 0;
> -	int ret2 = 0;
> 
>  	dump_completed_IO(inode);
>  	spin_lock_irqsave(&ei->i_completed_io_lock, flags);
> @@ -105,12 +104,10 @@ int ext4_flush_completed_IO(struct inode *inode)
>  		 */
>  		spin_unlock_irqrestore(&ei->i_completed_io_lock, flags);
>  		ret = ext4_end_io_nolock(io);
> -		if (ret < 0)
> -			ret2 = ret;
>  		spin_lock_irqsave(&ei->i_completed_io_lock, flags);
>  	}
>  	spin_unlock_irqrestore(&ei->i_completed_io_lock, flags);
> -	return (ret2 < 0) ? ret2 : 0;
> +	return (ret < 0) ? ret : 0;
>  }

Please note that there is a while loop involved here. Which means, that ret2
is used to store the last negative value of ret. And due to the loop, ret can
be over-written in the next loop iteration, which we can afford, because we
have already stored what we need to save, in ret2. And this ret2 value is used
to return appropriate value to the caller. 

Thanks,
Srivatsa S. Bhat

--
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/