public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "J . Bruce Fields" <bfields@fieldses.org>
To: Zhen Lei <thunder.leizhen@huawei.com>
Cc: Chuck Lever <chuck.lever@oracle.com>,
	linux-nfs <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 1/1] nfsd: remove unnecessary oom message
Date: Wed, 23 Jun 2021 17:41:15 -0400	[thread overview]
Message-ID: <20210623214115.GH20232@fieldses.org> (raw)
In-Reply-To: <20210617090458.1491-1-thunder.leizhen@huawei.com>

On Thu, Jun 17, 2021 at 05:04:57PM +0800, Zhen Lei wrote:
> Fixes scripts/checkpatch.pl warning:
> WARNING: Possible unnecessary 'out of memory' message
> 
> Remove it can help us save a bit of memory.

On a quick check, I think the other 6 pr_err()s in here also (pretty
unlikely) allocation failures, may as well remove those too?

--b.

> Signed-off-by: Zhen Lei <thunder.leizhen@huawei.com>
> ---
>  fs/nfsd/filecache.c | 4 +---
>  1 file changed, 1 insertion(+), 3 deletions(-)
> 
> diff --git a/fs/nfsd/filecache.c b/fs/nfsd/filecache.c
> index 7629248fdd53..76d68b2b4ba2 100644
> --- a/fs/nfsd/filecache.c
> +++ b/fs/nfsd/filecache.c
> @@ -643,10 +643,8 @@ nfsd_file_cache_init(void)
>  
>  	nfsd_file_hashtbl = kcalloc(NFSD_FILE_HASH_SIZE,
>  				sizeof(*nfsd_file_hashtbl), GFP_KERNEL);
> -	if (!nfsd_file_hashtbl) {
> -		pr_err("nfsd: unable to allocate nfsd_file_hashtbl\n");
> +	if (!nfsd_file_hashtbl)
>  		goto out_err;
> -	}
>  
>  	nfsd_file_slab = kmem_cache_create("nfsd_file",
>  				sizeof(struct nfsd_file), 0, 0, NULL);
> -- 
> 2.25.1
> 

      reply	other threads:[~2021-06-23 21:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-17  9:04 [PATCH 1/1] nfsd: remove unnecessary oom message Zhen Lei
2021-06-23 21:41 ` J . Bruce Fields [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=20210623214115.GH20232@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=thunder.leizhen@huawei.com \
    /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