From: kbuild test robot <lkp@intel.com>
To: "J. Bruce Fields" <bfields@redhat.com>
Cc: kbuild-all@01.org, Jeff Layton <jlayton@kernel.org>,
linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [linux-next:master 11868/13492] fs/nfsd/nfs4state.c:2508:6: sparse: sparse: symbol 'force_expire_client' was not declared. Should it be static?
Date: Wed, 10 Jul 2019 01:32:17 +0800 [thread overview]
Message-ID: <201907100149.XLk4C7WJ%lkp@intel.com> (raw)
tree: https://kernel.googlesource.com/pub/scm/linux/kernel/git/next/linux-next.git master
head: 4608a726c66807c27bc7d91bdf8a288254e29985
commit: 89c905beccbbafa88490c8c4c35eaec5ce4c1329 [11868/13492] nfsd: allow forced expiration of NFSv4 clients
reproduce:
# apt-get install sparse
# sparse version: v0.6.1-rc1-7-g2b96cd8-dirty
git checkout 89c905beccbbafa88490c8c4c35eaec5ce4c1329
make ARCH=x86_64 allmodconfig
make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
fs/nfsd/nfs4state.c:2352:23: sparse: sparse: unknown escape sequence: '%'
fs/nfsd/nfs4state.c:2352:23: sparse: sparse: unknown escape sequence: '%'
fs/nfsd/nfs4state.c:2355:23: sparse: sparse: unknown escape sequence: '%'
fs/nfsd/nfs4state.c:2355:23: sparse: sparse: unknown escape sequence: '%'
fs/nfsd/nfs4state.c:1907:6: sparse: sparse: symbol 'drop_client' was not declared. Should it be static?
>> fs/nfsd/nfs4state.c:2508:6: sparse: sparse: symbol 'force_expire_client' was not declared. Should it be static?
include/linux/rculist.h:455:20: sparse: sparse: context imbalance in 'put_nfs4_file' - unexpected unlock
include/linux/list.h:125:25: sparse: sparse: context imbalance in 'put_clnt_odstate' - unexpected unlock
fs/nfsd/nfs4state.c:915:9: sparse: sparse: context imbalance in 'nfs4_put_stid' - unexpected unlock
Please review and possibly fold the followup patch.
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
next reply other threads:[~2019-07-09 17:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-09 17:32 kbuild test robot [this message]
2019-07-09 17:32 ` [RFC PATCH linux-next] nfsd: force_expire_client() can be static kbuild test robot
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=201907100149.XLk4C7WJ%lkp@intel.com \
--to=lkp@intel.com \
--cc=bfields@redhat.com \
--cc=jlayton@kernel.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.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).