From: kernel test robot <lkp@intel.com>
To: Dai Ngo <dai.ngo@oracle.com>, bfields@fieldses.org
Cc: kbuild-all@lists.01.org, linux-nfs@vger.kernel.org
Subject: Re: [PATCH v2 1/1] NFSv4.2: Fix NFS4ERR_STALE error when doing inter server copy
Date: Thu, 8 Oct 2020 11:11:25 +0800 [thread overview]
Message-ID: <202010081105.SKjZ9mNb-lkp@intel.com> (raw)
In-Reply-To: <20201008012513.89989-2-dai.ngo@oracle.com>
[-- Attachment #1: Type: text/plain, Size: 2602 bytes --]
Hi Dai,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on nfs/linux-next]
[also build test WARNING on nfsd/nfsd-next v5.9-rc8 next-20201007]
[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/0day-ci/linux/commits/Dai-Ngo/NFSv4-2-Fix-NFS4ERR_STALE-with-inter-server-copy/20201008-092931
base: git://git.linux-nfs.org/projects/trondmy/linux-nfs.git linux-next
config: i386-randconfig-s001-20201008 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.2-218-gc0e96d6d-dirty
# https://github.com/0day-ci/linux/commit/589c5501bac22055fafe42825de27f3cc1c82626
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Dai-Ngo/NFSv4-2-Fix-NFS4ERR_STALE-with-inter-server-copy/20201008-092931
git checkout 589c5501bac22055fafe42825de27f3cc1c82626
# save the attached .config to linux build tree
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=i386
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
echo
echo "sparse warnings: (new ones prefixed by >>)"
echo
>> fs/nfs/super.c:89:33: sparse: sparse: symbol 'nfs_ssc_clnt_ops_tbl' was not declared. Should it be static?
fs/nfs/super.c:1114:49: sparse: sparse: incorrect type in initializer (different address spaces) @@ expected struct rpc_xprt *xprt1 @@ got struct rpc_xprt [noderef] __rcu *cl_xprt @@
fs/nfs/super.c:1114:49: sparse: expected struct rpc_xprt *xprt1
fs/nfs/super.c:1114:49: sparse: got struct rpc_xprt [noderef] __rcu *cl_xprt
fs/nfs/super.c:1115:49: sparse: sparse: incorrect type in initializer (different address spaces) @@ expected struct rpc_xprt *xprt2 @@ got struct rpc_xprt [noderef] __rcu *cl_xprt @@
fs/nfs/super.c:1115:49: sparse: expected struct rpc_xprt *xprt2
fs/nfs/super.c:1115:49: sparse: got struct rpc_xprt [noderef] __rcu *cl_xprt
fs/nfs/super.c:1335:14: sparse: sparse: symbol 'nfs_idmap_cache_timeout' was not declared. Should it be static?
--
>> fs/nfs/nfs4file.c:31:34: sparse: sparse: symbol 'nfs4_ssc_clnt_ops_tbl' was not declared. Should it be static?
Please review and possibly fold the followup patch.
---
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: 34975 bytes --]
next prev parent reply other threads:[~2020-10-08 3:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-08 1:25 [PATCH v2 0/1] NFSv4.2: Fix NFS4ERR_STALE with inter server copy Dai Ngo
2020-10-08 1:25 ` [PATCH v2 1/1] NFSv4.2: Fix NFS4ERR_STALE error when doing " Dai Ngo
2020-10-08 2:56 ` kernel test robot
2020-10-08 3:11 ` kernel test robot [this message]
2020-10-08 3:11 ` [RFC PATCH] NFSv4.2: nfs_ssc_clnt_ops_tbl can be static kernel test robot
2020-10-08 3:24 ` [PATCH v2 1/1] NFSv4.2: Fix NFS4ERR_STALE error when doing inter server copy kernel test robot
2020-10-08 17:58 ` [PATCH v2 0/1] NFSv4.2: Fix NFS4ERR_STALE with " J. Bruce Fields
2020-10-08 18:29 ` Dai Ngo
2020-10-08 19:47 ` J. Bruce Fields
2020-10-08 21:15 ` Dai Ngo
2020-10-08 21:17 ` Dai Ngo
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=202010081105.SKjZ9mNb-lkp@intel.com \
--to=lkp@intel.com \
--cc=bfields@fieldses.org \
--cc=dai.ngo@oracle.com \
--cc=kbuild-all@lists.01.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;
as well as URLs for NNTP newsgroup(s).