public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Anna Schumaker <Anna.Schumaker@netapp.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: fs/nfs/read.c:51:2-7: WARNING: NULL check before some freeing functions is not needed.
Date: Fri, 22 Mar 2024 23:44:04 +0800	[thread overview]
Message-ID: <202403222313.MSx9nW9B-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   8e938e39866920ddc266898e6ae1fffc5c8f51aa
commit: 303a78052091c81e9003915c521fdca1c7e117af NFSv4.2: Rework scratch handling for READ_PLUS (again)
date:   7 months ago
config: x86_64-randconfig-101-20240322 (https://download.01.org/0day-ci/archive/20240322/202403222313.MSx9nW9B-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202403222313.MSx9nW9B-lkp@intel.com/

cocci warnings: (new ones prefixed by >>)
>> fs/nfs/read.c:51:2-7: WARNING: NULL check before some freeing functions is not needed.

vim +51 fs/nfs/read.c

    47	
    48	static void nfs_readhdr_free(struct nfs_pgio_header *rhdr)
    49	{
    50		if (rhdr->res.scratch != NULL)
  > 51			kfree(rhdr->res.scratch);
    52		kmem_cache_free(nfs_rdata_cachep, rhdr);
    53	}
    54	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2024-03-22 15:44 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202403222313.MSx9nW9B-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=Anna.Schumaker@netapp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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