linux-kernel - Re: [PATCH 1/1 linux-next] udf: remove bool assignment to 0/1

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] [day] [month] [year] [list]

Message-ID: <20150205153714.GJ4258@quack.suse.cz>
Date:	Thu, 5 Feb 2015 16:37:14 +0100
From:	Jan Kara <jack@...e.cz>
To:	Fabian Frederick <fabf@...net.be>
Cc:	linux-kernel@...r.kernel.org, Jan Kara <jack@...e.cz>
Subject: Re: [PATCH 1/1 linux-next] udf: remove bool assignment to 0/1

On Wed 04-02-15 18:26:27, Fabian Frederick wrote:
> Fix the following coccinelle warnings:
> 
> fs/udf/inode.c:753:2-13: WARNING: Assignment of bool to 0/1
> fs/udf/inode.c:795:2-13: WARNING: Assignment of bool to 0/1
  Thanks for the fix. Patch merged.

								Honza

> 
> Signed-off-by: Fabian Frederick <fabf@...net.be>
> ---
>  fs/udf/inode.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/fs/udf/inode.c b/fs/udf/inode.c
> index 7b72b7d..a445d59 100644
> --- a/fs/udf/inode.c
> +++ b/fs/udf/inode.c
> @@ -750,7 +750,7 @@ static sector_t inode_getblk(struct inode *inode, sector_t block,
>  	/* Are we beyond EOF? */
>  	if (etype == -1) {
>  		int ret;
> -		isBeyondEOF = 1;
> +		isBeyondEOF = true;
>  		if (count) {
>  			if (c)
>  				laarr[0] = laarr[1];
> @@ -792,7 +792,7 @@ static sector_t inode_getblk(struct inode *inode, sector_t block,
>  		endnum = c + 1;
>  		lastblock = 1;
>  	} else {
> -		isBeyondEOF = 0;
> +		isBeyondEOF = false;
>  		endnum = startnum = ((count > 2) ? 2 : count);
>  
>  		/* if the current extent is in position 0,
> -- 
> 1.9.3
> 
-- 
Jan Kara <jack@...e.cz>
SUSE Labs, CR
--
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/