From: kernel test robot <lkp@intel.com>
To: Jeff Layton <jlayton@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [jlayton:dir-deleg 14/25] fs/nfsd/nfs4state.c:9911:1: error: conflicting types for 'nfsd4_run_cb_notify'
Date: Thu, 09 Apr 2026 06:02:34 +0200 [thread overview]
Message-ID: <202604090534.tunlxR45-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux.git dir-deleg
head: f46f4f860e384a5bc2c7a8f2fa64872ba4e303a5
commit: 748b5689ecabe0a80846c79cc0b468005b4d7e19 [14/25] nfsd: add notification handlers for dir events
config: x86_64-kexec (https://download.01.org/0day-ci/archive/20260409/202604090534.tunlxR45-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260409/202604090534.tunlxR45-lkp@intel.com/reproduce)
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/202604090534.tunlxR45-lkp@intel.com/
All errors (new ones prefixed by >>):
fs/nfsd/nfs4state.c:3583:3: error: call to undeclared function 'nfsd4_run_cb_notify'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
3583 | nfsd4_run_cb_notify(ncn);
| ^
>> fs/nfsd/nfs4state.c:9911:1: error: conflicting types for 'nfsd4_run_cb_notify'
9911 | nfsd4_run_cb_notify(struct nfsd4_cb_notify *ncn)
| ^
fs/nfsd/nfs4state.c:3583:3: note: previous implicit declaration is here
3583 | nfsd4_run_cb_notify(ncn);
| ^
2 errors generated.
vim +/nfsd4_run_cb_notify +9911 fs/nfsd/nfs4state.c
9909
9910 static void
> 9911 nfsd4_run_cb_notify(struct nfsd4_cb_notify *ncn)
9912 {
9913 struct nfs4_delegation *dp = container_of(ncn, struct nfs4_delegation, dl_cb_notify);
9914
9915 if (test_and_set_bit(NFSD4_CALLBACK_RUNNING, &ncn->ncn_cb.cb_flags))
9916 return;
9917
9918 if (!refcount_inc_not_zero(&dp->dl_stid.sc_count))
9919 clear_bit(NFSD4_CALLBACK_RUNNING, &ncn->ncn_cb.cb_flags);
9920 else
9921 nfsd4_run_cb(&ncn->ncn_cb);
9922 }
9923
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-04-09 4:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 4:02 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-04-10 16:35 [jlayton:dir-deleg 14/25] fs/nfsd/nfs4state.c:9911:1: error: conflicting types for 'nfsd4_run_cb_notify' kernel 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=202604090534.tunlxR45-lkp@intel.com \
--to=lkp@intel.com \
--cc=jlayton@kernel.org \
--cc=llvm@lists.linux.dev \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.