Linux NFS development
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
	Chuck Lever <chuck.lever@oracle.com>
Cc: linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
	Dan Carpenter <dan.carpenter@oracle.com>,
	linux-nfs@vger.kernel.org
Subject: Re: [PATCH v2 2/3] nfsd: Avoid some useless tests
Date: Thu, 01 Sep 2022 07:22:20 -0400	[thread overview]
Message-ID: <e9fef086c63de6388d038918ff5a71099c654fc1.camel@kernel.org> (raw)
In-Reply-To: <567c75570345fee506fb56d0c13cf9369931100a.1662009844.git.christophe.jaillet@wanadoo.fr>

On Thu, 2022-09-01 at 07:27 +0200, Christophe JAILLET wrote:
> memdup_user() can't return NULL, so there is no point for checking for it.
> 
> Simplify some tests accordingly.
> 
> Suggested-by: Dan Carpenter <dan.carpenter@oracle.com>
> Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
> ---
>  fs/nfsd/nfs4recover.c | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/fs/nfsd/nfs4recover.c b/fs/nfsd/nfs4recover.c
> index 248ff9f4141c..2968cf604e3b 100644
> --- a/fs/nfsd/nfs4recover.c
> +++ b/fs/nfsd/nfs4recover.c
> @@ -807,7 +807,7 @@ __cld_pipe_inprogress_downcall(const struct cld_msg_v2 __user *cmsg,
>  			if (get_user(namelen, &ci->cc_name.cn_len))
>  				return -EFAULT;
>  			name.data = memdup_user(&ci->cc_name.cn_id, namelen);
> -			if (IS_ERR_OR_NULL(name.data))
> +			if (IS_ERR(name.data))
>  				return -EFAULT;
>  			name.len = namelen;
>  			get_user(princhashlen, &ci->cc_princhash.cp_len);
> @@ -815,7 +815,7 @@ __cld_pipe_inprogress_downcall(const struct cld_msg_v2 __user *cmsg,
>  				princhash.data = memdup_user(
>  						&ci->cc_princhash.cp_data,
>  						princhashlen);
> -				if (IS_ERR_OR_NULL(princhash.data)) {
> +				if (IS_ERR(princhash.data)) {
>  					kfree(name.data);
>  					return -EFAULT;
>  				}
> @@ -829,7 +829,7 @@ __cld_pipe_inprogress_downcall(const struct cld_msg_v2 __user *cmsg,
>  			if (get_user(namelen, &cnm->cn_len))
>  				return -EFAULT;
>  			name.data = memdup_user(&cnm->cn_id, namelen);
> -			if (IS_ERR_OR_NULL(name.data))
> +			if (IS_ERR(name.data))
>  				return -EFAULT;
>  			name.len = namelen;
>  		}

Reviewed-by: Jeff Layton <jlayton@kernel.org>

  reply	other threads:[~2022-09-01 11:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-01  5:27 [PATCH v2 1/3] nfsd: Fix a memory leak in an error handling path Christophe JAILLET
2022-09-01  5:27 ` [PATCH v2 2/3] nfsd: Avoid some useless tests Christophe JAILLET
2022-09-01 11:22   ` Jeff Layton [this message]
2022-09-01  5:27 ` [PATCH v2 3/3] nfsd: Propagate some error code returned by memdup_user() Christophe JAILLET
2022-09-01 11:25   ` Jeff Layton
2022-09-01 11:21 ` [PATCH v2 1/3] nfsd: Fix a memory leak in an error handling path Jeff Layton
2022-09-01 16:24   ` Chuck Lever III

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=e9fef086c63de6388d038918ff5a71099c654fc1.camel@kernel.org \
    --to=jlayton@kernel.org \
    --cc=christophe.jaillet@wanadoo.fr \
    --cc=chuck.lever@oracle.com \
    --cc=dan.carpenter@oracle.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@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