From: kernel test robot <lkp@intel.com>
To: Javier Abrego <javier.abrego.lorente@gmail.com>,
trond.myklebust@hammerspace.com, anna@kernel.org
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org,
javier.abrego.lorente@gmail.com
Subject: Re: [PATCH] FS: nfs: removed goto statement
Date: Fri, 20 May 2022 11:58:46 +0800 [thread overview]
Message-ID: <202205201106.ONDKuLvW-lkp@intel.com> (raw)
In-Reply-To: <20220519225115.35431-1-javier.abrego.lorente@gmail.com>
Hi Javier,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on trondmy-nfs/linux-next]
[also build test WARNING on v5.18-rc7 next-20220519]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/intel-lab-lkp/linux/commits/Javier-Abrego/FS-nfs-removed-goto-statement/20220520-065648
base: git://git.linux-nfs.org/projects/trondmy/linux-nfs.git linux-next
config: i386-randconfig-a015 (https://download.01.org/0day-ci/archive/20220520/202205201106.ONDKuLvW-lkp@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project e00cbbec06c08dc616a0d52a20f678b8fbd4e304)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/intel-lab-lkp/linux/commit/99dd76e4af5d61f97c1981a240cbd1d86908ac8e
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Javier-Abrego/FS-nfs-removed-goto-statement/20220520-065648
git checkout 99dd76e4af5d61f97c1981a240cbd1d86908ac8e
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=i386 SHELL=/bin/bash fs/nfs/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> fs/nfs/nfs42xattr.c:754:3: warning: variable 'entry' is uninitialized when used here [-Wuninitialized]
entry->bucket = &cache->buckets[0];
^~~~~
fs/nfs/nfs42xattr.c:743:32: note: initialize the variable 'entry' to silence this warning
struct nfs4_xattr_entry *entry;
^
= NULL
1 warning generated.
vim +/entry +754 fs/nfs/nfs42xattr.c
95ad37f90c338e Frank van der Linden 2020-06-23 735
95ad37f90c338e Frank van der Linden 2020-06-23 736 /*
95ad37f90c338e Frank van der Linden 2020-06-23 737 * Cache listxattr output, replacing any possible old one.
95ad37f90c338e Frank van der Linden 2020-06-23 738 */
95ad37f90c338e Frank van der Linden 2020-06-23 739 void nfs4_xattr_cache_set_list(struct inode *inode, const char *buf,
95ad37f90c338e Frank van der Linden 2020-06-23 740 ssize_t buflen)
95ad37f90c338e Frank van der Linden 2020-06-23 741 {
95ad37f90c338e Frank van der Linden 2020-06-23 742 struct nfs4_xattr_cache *cache;
95ad37f90c338e Frank van der Linden 2020-06-23 743 struct nfs4_xattr_entry *entry;
95ad37f90c338e Frank van der Linden 2020-06-23 744
95ad37f90c338e Frank van der Linden 2020-06-23 745 cache = nfs4_xattr_get_cache(inode, 1);
99dd76e4af5d61 Javier Abrego 2022-05-20 746 if (cache == NULL) {
99dd76e4af5d61 Javier Abrego 2022-05-20 747 kref_put(&cache->ref, nfs4_xattr_free_cache_cb);
99dd76e4af5d61 Javier Abrego 2022-05-20 748 } else {
95ad37f90c338e Frank van der Linden 2020-06-23 749 /*
95ad37f90c338e Frank van der Linden 2020-06-23 750 * This is just there to be able to get to bucket->cache,
95ad37f90c338e Frank van der Linden 2020-06-23 751 * which is obviously the same for all buckets, so just
95ad37f90c338e Frank van der Linden 2020-06-23 752 * use bucket 0.
95ad37f90c338e Frank van der Linden 2020-06-23 753 */
95ad37f90c338e Frank van der Linden 2020-06-23 @754 entry->bucket = &cache->buckets[0];
95ad37f90c338e Frank van der Linden 2020-06-23 755
95ad37f90c338e Frank van der Linden 2020-06-23 756 if (!nfs4_xattr_set_listcache(cache, entry))
95ad37f90c338e Frank van der Linden 2020-06-23 757 kref_put(&entry->ref, nfs4_xattr_free_entry_cb);
99dd76e4af5d61 Javier Abrego 2022-05-20 758 }
95ad37f90c338e Frank van der Linden 2020-06-23 759 }
95ad37f90c338e Frank van der Linden 2020-06-23 760
--
0-DAY CI Kernel Test Service
https://01.org/lkp
next prev parent reply other threads:[~2022-05-20 3:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-19 22:51 [PATCH] FS: nfs: removed goto statement Javier Abrego
2022-05-19 23:49 ` Frank van der Linden
2022-05-20 0:18 ` Trond Myklebust
2022-05-20 3:58 ` kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-05-20 8:50 Javier Abrego
2022-05-20 11:57 Javier Abrego
2022-05-20 12:00 ` Javier Abrego Lorente
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=202205201106.ONDKuLvW-lkp@intel.com \
--to=lkp@intel.com \
--cc=anna@kernel.org \
--cc=javier.abrego.lorente@gmail.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=trond.myklebust@hammerspace.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;
as well as URLs for NNTP newsgroup(s).