From: kernel test robot <lkp@intel.com>
To: Dai Ngo <dai.ngo@oracle.com>
Cc: kbuild-all@lists.01.org, clang-built-linux@googlegroups.com,
Linux Memory Management List <linux-mm@kvack.org>,
Chuck Lever <chuck.lever@oracle.com>
Subject: [linux-next:master 6011/11791] fs/nfs/super.c:90:40: warning: unused variable 'nfs_ssc_clnt_ops_tbl'
Date: Fri, 19 Feb 2021 21:04:06 +0800 [thread overview]
Message-ID: <202102192159.vSI24Z2E-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2680 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: ff90dfd2579b2c7bc1f0baa0cb99c918c6c1ec64
commit: 02591f9febd5f69bb4c266a4abf899c4cf21964f [6011/11791] NFSv4_2: SSC helper should use its own config.
config: x86_64-randconfig-r034-20210219 (attached as .config)
compiler: clang version 12.0.0 (https://github.com/llvm/llvm-project c9439ca36342fb6013187d0a69aef92736951476)
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
# install x86_64 cross compiling tool for clang build
# apt-get install binutils-x86-64-linux-gnu
# https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=02591f9febd5f69bb4c266a4abf899c4cf21964f
git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git fetch --no-tags linux-next master
git checkout 02591f9febd5f69bb4c266a4abf899c4cf21964f
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=x86_64
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/super.c:90:40: warning: unused variable 'nfs_ssc_clnt_ops_tbl' [-Wunused-const-variable]
static const struct nfs_ssc_client_ops nfs_ssc_clnt_ops_tbl = {
^
1 warning generated.
--
>> fs/nfs/nfs4file.c:410:41: warning: unused variable 'nfs4_ssc_clnt_ops_tbl' [-Wunused-const-variable]
static const struct nfs4_ssc_client_ops nfs4_ssc_clnt_ops_tbl = {
^
1 warning generated.
vim +/nfs_ssc_clnt_ops_tbl +90 fs/nfs/super.c
f7b422b17ee5ee David Howells 2006-06-09 88
02591f9febd5f6 Dai Ngo 2021-01-28 89 #ifdef CONFIG_NFS_V4_2
0cfcd405e758ba Dai Ngo 2020-10-18 @90 static const struct nfs_ssc_client_ops nfs_ssc_clnt_ops_tbl = {
0cfcd405e758ba Dai Ngo 2020-10-18 91 .sco_sb_deactive = nfs_sb_deactive,
0cfcd405e758ba Dai Ngo 2020-10-18 92 };
02591f9febd5f6 Dai Ngo 2021-01-28 93 #endif
0cfcd405e758ba Dai Ngo 2020-10-18 94
:::::: The code at line 90 was first introduced by commit
:::::: 0cfcd405e758ba1d277e58436fb32f06888c3e41 NFSv4.2: Fix NFS4ERR_STALE error when doing inter server copy
:::::: TO: Dai Ngo <dai.ngo@oracle.com>
:::::: CC: J. Bruce Fields <bfields@redhat.com>
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 41777 bytes --]
next reply other threads:[~2021-02-19 13:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-19 13:04 kernel test robot [this message]
2021-02-22 20:02 ` [linux-next:master 6011/11791] fs/nfs/super.c:90:40: warning: unused variable 'nfs_ssc_clnt_ops_tbl' Souptick Joarder
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=202102192159.vSI24Z2E-lkp@intel.com \
--to=lkp@intel.com \
--cc=chuck.lever@oracle.com \
--cc=clang-built-linux@googlegroups.com \
--cc=dai.ngo@oracle.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.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;
as well as URLs for NNTP newsgroup(s).