linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Julia Lawall <julia.lawall@lip6.fr>
Cc: linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org,
	kbuild-all@01.org
Subject: Re: [PATCH] xfs: fix returnvar.cocci warnings
Date: Thu, 26 Jan 2017 10:30:56 -0800	[thread overview]
Message-ID: <20170126183056.GV9134@birch.djwong.org> (raw)
In-Reply-To: <alpine.DEB.2.20.1701261019430.3109@hadrien>

On Thu, Jan 26, 2017 at 10:20:58AM +0100, Julia Lawall wrote:
> Remove unneeded variable used to store return value.
> 
> Generated by: scripts/coccinelle/misc/returnvar.cocci
> 
> Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
> ---
> 
> Is it correct to be returning 0 in the level == 0 case?

Yes, because level == 0 is the root node for xfs dir/attr btree cursors
(which is confusing since level == 0 are leaf nodes for the regular xfs
btree cursors).  Therefore if level == 0 we're at the root and there are
no parent hash values to check.

That said, you're absolutely right that we don't need the intermediate
variable in either function.

--D

> 
>  dabtree.c |    9 +++------
>  1 file changed, 3 insertions(+), 6 deletions(-)
> 
> --- a/fs/xfs/scrub/dabtree.c
> +++ b/fs/xfs/scrub/dabtree.c
> @@ -96,7 +96,6 @@ xfs_scrub_da_btree_hash(
>  	struct xfs_da_node_entry	*btree;
>  	xfs_dahash_t			hash;
>  	xfs_dahash_t			parent_hash;
> -	int				error = 0;
> 
>  	/* Is this hash in order? */
>  	hash = be32_to_cpu(*hashp);
> @@ -104,7 +103,7 @@ xfs_scrub_da_btree_hash(
>  	ds->hashes[level] = hash;
> 
>  	if (level == 0)
> -		return error;
> +		return 0;
> 
>  	/* Is this hash no larger than the parent hash? */
>  	blks = ds->state->path.blk;
> @@ -112,7 +111,7 @@ xfs_scrub_da_btree_hash(
>  	parent_hash = be32_to_cpu(btree->hashval);
>  	XFS_SCRUB_DA_CHECK(ds, hash <= parent_hash);
> 
> -	return error;
> +	return 0;
>  }
> 
>  /* Scrub a da btree pointer. */
> @@ -122,12 +121,10 @@ xfs_scrub_da_btree_ptr(
>  	int				level,
>  	xfs_dablk_t			blkno)
>  {
> -	int				error = 0;
> -
>  	XFS_SCRUB_DA_CHECK(ds, blkno >= ds->lowest);
>  	XFS_SCRUB_DA_CHECK(ds, ds->highest == 0 || blkno < ds->highest);
> 
> -	return error;
> +	return 0;
>  }
> 
>  /*
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2017-01-26 18:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-26  9:20 [PATCH] xfs: fix returnvar.cocci warnings Julia Lawall
2017-01-26 18:30 ` Darrick J. Wong [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=20170126183056.GV9134@birch.djwong.org \
    --to=darrick.wong@oracle.com \
    --cc=julia.lawall@lip6.fr \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@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;
as well as URLs for NNTP newsgroup(s).