public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Andrey Strachuk <strochuk@ispras.ru>
Cc: Dave Chinner <dchinner@redhat.com>,
	Allison Henderson <allison.henderson@oracle.com>,
	Chandan Babu R <chandan.babu@oracle.com>,
	linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org,
	ldv-project@linuxtesting.org
Subject: Re: [PATCH] xfs: removed useless condition in function xfs_attr_node_get
Date: Wed, 6 Jul 2022 10:11:17 -0700	[thread overview]
Message-ID: <YsXCNSIeP9y9S2fa@magnolia> (raw)
In-Reply-To: <20220706133627.11198-1-strochuk@ispras.ru>

On Wed, Jul 06, 2022 at 04:36:27PM +0300, Andrey Strachuk wrote:
> At line 1561, variable "state" is being compared
> with NULL every loop iteration.
> 
> -------------------------------------------------------------------
> 1561	for (i = 0; state != NULL && i < state->path.active; i++) {
> 1562		xfs_trans_brelse(args->trans, state->path.blk[i].bp);
> 1563		state->path.blk[i].bp = NULL;
> 1564	}
> -------------------------------------------------------------------
> 
> However, it cannot be NULL.
> 
> ----------------------------------------
> 1546	state = xfs_da_state_alloc(args);
> ----------------------------------------
> 
> xfs_da_state_alloc calls kmem_cache_zalloc. kmem_cache_zalloc is
> called with __GFP_NOFAIL flag and, therefore, it cannot return NULL.
> 
> --------------------------------------------------------------------------
> 	struct xfs_da_state *
> 	xfs_da_state_alloc(
> 	struct xfs_da_args	*args)
> 	{
> 		struct xfs_da_state	*state;
> 
> 		state = kmem_cache_zalloc(xfs_da_state_cache, GFP_NOFS | __GFP_NOFAIL);
> 		state->args = args;
> 		state->mp = args->dp->i_mount;
> 		return state;
> 	}
> --------------------------------------------------------------------------
> 
> Found by Linux Verification Center (linuxtesting.org) with SVACE.
> 
> Signed-off-by: Andrey Strachuk <strochuk@ispras.ru>
> 
> Fixes: 4d0cdd2bb8f0 ("xfs: clean up xfs_attr_node_hasname")

Nit: usually the tags go at the end with no empty lines between them.

The change looks correct to me, so
Reviewed-by: Darrick J. Wong <djwong@kernel.org>

--D

> ---
>  fs/xfs/libxfs/xfs_attr.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/fs/xfs/libxfs/xfs_attr.c b/fs/xfs/libxfs/xfs_attr.c
> index 224649a76cbb..6b8857e53add 100644
> --- a/fs/xfs/libxfs/xfs_attr.c
> +++ b/fs/xfs/libxfs/xfs_attr.c
> @@ -1558,7 +1558,7 @@ xfs_attr_node_get(
>  	 * If not in a transaction, we have to release all the buffers.
>  	 */
>  out_release:
> -	for (i = 0; state != NULL && i < state->path.active; i++) {
> +	for (i = 0; i < state->path.active; i++) {
>  		xfs_trans_brelse(args->trans, state->path.blk[i].bp);
>  		state->path.blk[i].bp = NULL;
>  	}
> -- 
> 2.25.1
> 

      reply	other threads:[~2022-07-06 17:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-06 13:36 [PATCH] xfs: removed useless condition in function xfs_attr_node_get Andrey Strachuk
2022-07-06 17:11 ` 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=YsXCNSIeP9y9S2fa@magnolia \
    --to=djwong@kernel.org \
    --cc=allison.henderson@oracle.com \
    --cc=chandan.babu@oracle.com \
    --cc=dchinner@redhat.com \
    --cc=ldv-project@linuxtesting.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=strochuk@ispras.ru \
    /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