From: kernel test robot <lkp@intel.com>
To: Dave Wysochanski <dwysocha@redhat.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
linux-kernel@vger.kernel.org, David Howells <dhowells@redhat.com>
Subject: [dhowells-fs:fscache-rewrite 64/69] fs/nfs/file.c:87:2: error: implicit declaration of function 'nfs_fscache_release_file'
Date: Fri, 10 Dec 2021 09:51:54 +0800 [thread overview]
Message-ID: <202112100931.6qc8V8T4-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git fscache-rewrite
head: 82abe23a0865faea23cf06ac51f2303f26b9bb53
commit: 57858b0feb9a11f6d9b5720cdd13222098f9e59f [64/69] nfs: Convert to new fscache volume/cookie API
config: x86_64-randconfig-a011-20211209 (https://download.01.org/0day-ci/archive/20211210/202112100931.6qc8V8T4-lkp@intel.com/config)
compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project 097a1cb1d5ebb3a0ec4bcaed8ba3ff6a8e33c00a)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/commit/?id=57858b0feb9a11f6d9b5720cdd13222098f9e59f
git remote add dhowells-fs https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git
git fetch --no-tags dhowells-fs fscache-rewrite
git checkout 57858b0feb9a11f6d9b5720cdd13222098f9e59f
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash fs/nfs/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> fs/nfs/file.c:87:2: error: implicit declaration of function 'nfs_fscache_release_file' [-Werror,-Wimplicit-function-declaration]
nfs_fscache_release_file(inode, filp);
^
fs/nfs/file.c:87:2: note: did you mean 'nfs_fscache_release_page'?
fs/nfs/fscache.h:154:19: note: 'nfs_fscache_release_page' declared here
static inline int nfs_fscache_release_page(struct page *page, gfp_t gfp)
^
1 error generated.
vim +/nfs_fscache_release_file +87 fs/nfs/file.c
79
80 int
81 nfs_file_release(struct inode *inode, struct file *filp)
82 {
83 dprintk("NFS: release(%pD2)\n", filp);
84
85 nfs_inc_stats(inode, NFSIOS_VFSRELEASE);
86 nfs_file_clear_open_context(filp);
> 87 nfs_fscache_release_file(inode, filp);
88 return 0;
89 }
90 EXPORT_SYMBOL_GPL(nfs_file_release);
91
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2021-12-10 1:52 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=202112100931.6qc8V8T4-lkp@intel.com \
--to=lkp@intel.com \
--cc=dhowells@redhat.com \
--cc=dwysocha@redhat.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@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