From: kernel test robot <lkp@intel.com>
To: David Howells <dhowells@redhat.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [dhowells-fs:fscache-iter-2 66/67] inode.c:undefined reference to `__fscache_invalidate'
Date: Wed, 29 Sep 2021 12:45:48 +0800 [thread overview]
Message-ID: <202109291243.rBf7qgEJ-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2836 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git fscache-iter-2
head: 23676c28d1a9add6ea09f19ca89b71be994a4b79
commit: be401b99396d9299b6e66ff061f722c275441d60 [66/67] nfs: Convert to new fscache volume/cookie API
config: x86_64-rhel-8.3 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/commit/?id=be401b99396d9299b6e66ff061f722c275441d60
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-iter-2
git checkout be401b99396d9299b6e66ff061f722c275441d60
# save the attached .config to linux build tree
mkdir build_dir
make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash
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 >>):
ld: fs/nfs/inode.o: in function `nfs_set_cache_invalid':
>> inode.c:(.text+0x9f8): undefined reference to `__fscache_invalidate'
ld: fs/nfs/inode.o: in function `nfs_clear_invalid_mapping':
inode.c:(.text+0x3afc): undefined reference to `__fscache_invalidate'
ld: fs/nfs/direct.o: in function `nfs_file_direct_write':
>> direct.c:(.text+0x1d44): undefined reference to `__fscache_invalidate'
ld: fs/nfs/write.o: in function `nfs_writepage_setup':
>> write.c:(.text+0x3d8f): undefined reference to `__fscache_invalidate'
ld: fs/nfs/fscache.o: in function `nfs_fscache_open_file':
>> fscache.c:(.text+0x128): undefined reference to `__fscache_unuse_cookie'
>> ld: fscache.c:(.text+0x162): undefined reference to `__fscache_use_cookie'
ld: fs/nfs/fscache.o: in function `nfs_fscache_get_super_cookie':
>> fscache.c:(.text+0x43b): undefined reference to `__fscache_acquire_volume'
ld: fs/nfs/fscache.o: in function `nfs_fscache_release_super_cookie':
>> fscache.c:(.text+0x52b): undefined reference to `__fscache_relinquish_volume'
ld: fs/nfs/fscache.o: in function `nfs_fscache_init_inode':
>> fscache.c:(.text+0x653): undefined reference to `__fscache_acquire_cookie'
ld: fs/nfs/fscache.o: in function `nfs_fscache_clear_inode':
>> fscache.c:(.text+0x6c6): undefined reference to `__fscache_relinquish_cookie'
>> ld: fscache.c:(.text+0x749): undefined reference to `__fscache_unuse_cookie'
ld: fs/nfs/fscache.o: in function `__nfs_readpage_from_fscache':
>> fscache.c:(.text+0x7c0): undefined reference to `__fscache_fallback_read_page'
ld: fs/nfs/fscache.o: in function `__nfs_readpage_to_fscache':
>> fscache.c:(.text+0x8b4): undefined reference to `__fscache_fallback_write_page'
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 40405 bytes --]
reply other threads:[~2021-09-29 4:46 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=202109291243.rBf7qgEJ-lkp@intel.com \
--to=lkp@intel.com \
--cc=dhowells@redhat.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®