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:nfsd-tracepoints 10/14] fs/nfsd/nfsproc.c:483:2: error: call to undeclared function 'trace_nfsd_proc_link'; ISO C99 and later do not support implicit function declarations
Date: Wed, 12 Mar 2025 03:43:54 +0800 [thread overview]
Message-ID: <202503120309.6UatC2Y3-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux.git nfsd-tracepoints
head: 406b15fe7fc917eb20c0cfe48d441442adad9918
commit: 0dde04bfb829ba259ce6f586a807eaaee6540529 [10/14] nfsd: add tracepoints for hardlink events
config: arm-randconfig-003-20250312 (https://download.01.org/0day-ci/archive/20250312/202503120309.6UatC2Y3-lkp@intel.com/config)
compiler: clang version 19.1.7 (https://github.com/llvm/llvm-project cd708029e0b2869e80abe31ddb175f7c35361f90)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250312/202503120309.6UatC2Y3-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/202503120309.6UatC2Y3-lkp@intel.com/
All errors (new ones prefixed by >>):
fs/nfsd/nfsproc.c:295:2: error: call to undeclared function 'trace_nfsd_proc_create'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
295 | trace_nfsd_proc_create(rqstp, dirfhp, S_IFREG, argp->name, argp->len);
| ^
fs/nfsd/nfsproc.c:295:2: note: did you mean 'nfsd_proc_create'?
fs/nfsd/nfsproc.c:279:1: note: 'nfsd_proc_create' declared here
279 | nfsd_proc_create(struct svc_rqst *rqstp)
| ^
>> fs/nfsd/nfsproc.c:483:2: error: call to undeclared function 'trace_nfsd_proc_link'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
483 | trace_nfsd_proc_link(rqstp, &argp->ffh, &argp->tfh, argp->tname, argp->tlen);
| ^
fs/nfsd/nfsproc.c:483:2: note: did you mean 'nfsd_proc_link'?
fs/nfsd/nfsproc.c:478:1: note: 'nfsd_proc_link' declared here
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);
| ~~~~~~~~~~~~~~~~~~~~
| nfsd_proc_link
fs/nfsd/nfsproc.c:503:2: error: call to undeclared function 'trace_nfsd_proc_symlink'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
503 | trace_nfsd_proc_symlink(rqstp, &argp->ffh, argp->fname, argp->flen,
| ^
fs/nfsd/nfsproc.c:503:2: note: did you mean 'nfsd_proc_symlink'?
fs/nfsd/nfsproc.c:494:1: note: 'nfsd_proc_symlink' declared here
494 | nfsd_proc_symlink(struct svc_rqst *rqstp)
| ^
495 | {
496 | struct nfsd_symlinkargs *argp = rqstp->rq_argp;
497 | struct nfsd_stat *resp = rqstp->rq_resp;
498 | struct nfsd_attrs attrs = {
499 | .na_iattr = &argp->attrs,
500 | };
501 | struct svc_fh newfh;
502 |
503 | trace_nfsd_proc_symlink(rqstp, &argp->ffh, argp->fname, argp->flen,
| ~~~~~~~~~~~~~~~~~~~~~~~
| nfsd_proc_symlink
fs/nfsd/nfsproc.c:538:1: error: function definition is not allowed here
538 | {
| ^
fs/nfsd/nfsproc.c:571:1: error: function definition is not allowed here
571 | {
| ^
fs/nfsd/nfsproc.c:587:1: error: function definition is not allowed here
587 | {
| ^
fs/nfsd/nfsproc.c:607:1: error: function definition is not allowed here
607 | {
| ^
fs/nfsd/nfsproc.c:635:1: error: function definition is not allowed here
635 | {
| ^
fs/nfsd/nfsproc.c:819:14: error: use of undeclared identifier 'nfsd_proc_mkdir'; did you mean '_proc_mkdir'?
819 | .pc_func = nfsd_proc_mkdir,
| ^~~~~~~~~~~~~~~
| _proc_mkdir
include/linux/proc_fs.h:85:24: note: '_proc_mkdir' declared here
85 | struct proc_dir_entry *_proc_mkdir(const char *, umode_t, struct proc_dir_entry *, void *, bool);
| ^
fs/nfsd/nfsproc.c:831:14: error: use of undeclared identifier 'nfsd_proc_rmdir'
831 | .pc_func = nfsd_proc_rmdir,
| ^
fs/nfsd/nfsproc.c:842:14: error: use of undeclared identifier 'nfsd_proc_readdir'
842 | .pc_func = nfsd_proc_readdir,
| ^
fs/nfsd/nfsproc.c:852:14: error: use of undeclared identifier 'nfsd_proc_statfs'; did you mean 'nfsd_proc_setattr'?
852 | .pc_func = nfsd_proc_statfs,
| ^~~~~~~~~~~~~~~~
| nfsd_proc_setattr
fs/nfsd/nfsproc.c:75:1: note: 'nfsd_proc_setattr' declared here
75 | nfsd_proc_setattr(struct svc_rqst *rqstp)
| ^
fs/nfsd/nfsproc.c:873:3: error: expected '}'
873 | };
| ^
fs/nfsd/nfsproc.c:495:1: note: to match this '{'
495 | {
| ^
13 errors generated.
vim +/trace_nfsd_proc_link +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 19:44 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=202503120309.6UatC2Y3-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