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:kdevops 74/81] fs/nfsd/nfsproc.c:483:9: error: implicit declaration of function 'trace_nfsd_proc_link'; did you mean 'nfsd_proc_link'?
Date: Wed, 12 Mar 2025 01:28:16 +0800 [thread overview]
Message-ID: <202503120154.ctwnAOLZ-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux.git kdevops
head: 86deeee9a2bdf8ba09cfd0ab66dbf448d2e8b82b
commit: c35bc37489cde3283951cb26a56b8b6aa77c151b [74/81] nfsd: add tracepoints for hardlink events
config: sparc-randconfig-001-20250311 (https://download.01.org/0day-ci/archive/20250312/202503120154.ctwnAOLZ-lkp@intel.com/config)
compiler: sparc-linux-gcc (GCC) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250312/202503120154.ctwnAOLZ-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/202503120154.ctwnAOLZ-lkp@intel.com/
All errors (new ones prefixed by >>):
fs/nfsd/nfsproc.c: In function 'nfsd_proc_create':
fs/nfsd/nfsproc.c:295:9: error: implicit declaration of function 'trace_nfsd_proc_create'; did you mean 'nfsd_proc_create'? [-Wimplicit-function-declaration]
295 | trace_nfsd_proc_create(rqstp, dirfhp, S_IFREG, argp->name, argp->len);
| ^~~~~~~~~~~~~~~~~~~~~~
| nfsd_proc_create
fs/nfsd/nfsproc.c: In function 'nfsd_proc_link':
>> fs/nfsd/nfsproc.c:483:9: error: implicit declaration of function 'trace_nfsd_proc_link'; did you mean 'nfsd_proc_link'? [-Wimplicit-function-declaration]
483 | trace_nfsd_proc_link(rqstp, &argp->ffh, &argp->tfh, argp->tname, argp->tlen);
| ^~~~~~~~~~~~~~~~~~~~
| nfsd_proc_link
fs/nfsd/nfsproc.c: In function 'nfsd_proc_symlink':
fs/nfsd/nfsproc.c:503:9: error: implicit declaration of function 'trace_nfsd_proc_symlink'; did you mean 'nfsd_proc_symlink'? [-Wimplicit-function-declaration]
503 | trace_nfsd_proc_symlink(rqstp, &argp->ffh, argp->fname, argp->flen,
| ^~~~~~~~~~~~~~~~~~~~~~~
| nfsd_proc_symlink
fs/nfsd/nfsproc.c:537:1: error: invalid storage class for function 'nfsd_proc_mkdir'
537 | nfsd_proc_mkdir(struct svc_rqst *rqstp)
| ^~~~~~~~~~~~~~~
fs/nfsd/nfsproc.c: In function 'nfsd_proc_mkdir':
fs/nfsd/nfsproc.c:545:9: error: implicit declaration of function 'trace_nfsd_proc_mkdir'; did you mean 'nfsd_proc_mkdir'? [-Wimplicit-function-declaration]
545 | trace_nfsd_proc_mkdir(rqstp, &argp->fh, S_IFDIR, argp->name, argp->len);
| ^~~~~~~~~~~~~~~~~~~~~
| nfsd_proc_mkdir
fs/nfsd/nfsproc.c: In function 'nfsd_proc_symlink':
fs/nfsd/nfsproc.c:570:1: error: invalid storage class for function 'nfsd_proc_rmdir'
570 | nfsd_proc_rmdir(struct svc_rqst *rqstp)
| ^~~~~~~~~~~~~~~
fs/nfsd/nfsproc.c:584:13: error: invalid storage class for function 'nfsd_init_dirlist_pages'
584 | static void nfsd_init_dirlist_pages(struct svc_rqst *rqstp,
| ^~~~~~~~~~~~~~~~~~~~~~~
fs/nfsd/nfsproc.c:606:1: error: invalid storage class for function 'nfsd_proc_readdir'
606 | nfsd_proc_readdir(struct svc_rqst *rqstp)
| ^~~~~~~~~~~~~~~~~
fs/nfsd/nfsproc.c:634:1: error: invalid storage class for function 'nfsd_proc_statfs'
634 | nfsd_proc_statfs(struct svc_rqst *rqstp)
| ^~~~~~~~~~~~~~~~
fs/nfsd/nfsproc.c:819:28: error: initializer element is not constant
819 | .pc_func = nfsd_proc_mkdir,
| ^~~~~~~~~~~~~~~
fs/nfsd/nfsproc.c:819:28: note: (near initialization for 'nfsd_procedures2[14].pc_func')
fs/nfsd/nfsproc.c:831:28: error: initializer element is not constant
831 | .pc_func = nfsd_proc_rmdir,
| ^~~~~~~~~~~~~~~
fs/nfsd/nfsproc.c:831:28: note: (near initialization for 'nfsd_procedures2[15].pc_func')
fs/nfsd/nfsproc.c:842:28: error: initializer element is not constant
842 | .pc_func = nfsd_proc_readdir,
| ^~~~~~~~~~~~~~~~~
fs/nfsd/nfsproc.c:842:28: note: (near initialization for 'nfsd_procedures2[16].pc_func')
fs/nfsd/nfsproc.c:852:28: error: initializer element is not constant
852 | .pc_func = nfsd_proc_statfs,
| ^~~~~~~~~~~~~~~~
fs/nfsd/nfsproc.c:852:28: note: (near initialization for 'nfsd_procedures2[17].pc_func')
fs/nfsd/nfsproc.c:873:1: error: expected declaration or statement at end of input
873 | };
| ^
fs/nfsd/nfsproc.c:866:26: warning: unused variable 'nfsd_version2' [-Wunused-variable]
866 | const struct svc_version nfsd_version2 = {
| ^~~~~~~~~~~~~
fs/nfsd/nfsproc.c: At top level:
fs/nfsd/nfsproc.c:494:1: warning: 'nfsd_proc_symlink' defined but not used [-Wunused-function]
494 | nfsd_proc_symlink(struct svc_rqst *rqstp)
| ^~~~~~~~~~~~~~~~~
vim +483 fs/nfsd/nfsproc.c
476
477 static __be32
478 nfsd_proc_link(struct svc_rqst *rqstp)
479 {
480 struct nfsd_linkargs *argp = rqstp->rq_argp;
481 struct nfsd_stat *resp = rqstp->rq_resp;
482
> 483 trace_nfsd_proc_link(rqstp, &argp->ffh, &argp->tfh, argp->tname, argp->tlen);
484
485 resp->status = nfsd_link(rqstp, &argp->tfh, argp->tname, argp->tlen,
486 &argp->ffh);
487 fh_put(&argp->ffh);
488 fh_put(&argp->tfh);
489 resp->status = nfsd_map_status(resp->status);
490 return rpc_success;
491 }
492
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-03-11 17:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202503120154.ctwnAOLZ-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox