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-rewrite-indexing 61/80] fs/afs/write.c:26: undefined reference to `fscache_set_page_dirty'
Date: Wed, 13 Oct 2021 08:09:53 +0800 [thread overview]
Message-ID: <202110130850.QpHC93Ek-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2082 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git fscache-rewrite-indexing
head: 5914ee72cd59ac43f27adae6340e8219592462d5
commit: 7fc886b896abeed2560da268c703bb6af87c8e89 [61/80] afs: Copy local writes to the cache when writing to the server
config: x86_64-randconfig-a001-20211012 (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=7fc886b896abeed2560da268c703bb6af87c8e89
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-indexing
git checkout 7fc886b896abeed2560da268c703bb6af87c8e89
# 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/afs/write.o: in function `afs_set_page_dirty':
>> fs/afs/write.c:26: undefined reference to `fscache_set_page_dirty'
ld: fs/afs/write.o: in function `fscache_clear_page_bits':
>> include/linux/fscache.h:563: undefined reference to `__fscache_clear_page_bits'
ld: fs/afs/write.o: in function `fscache_write_to_cache':
>> include/linux/fscache.h:595: undefined reference to `__fscache_write_to_cache'
vim +26 fs/afs/write.c
16
17 static void afs_write_to_cache(struct afs_vnode *vnode, loff_t start, size_t len,
18 loff_t i_size);
19
20 /*
21 * Mark a page as having been made dirty and thus needing writeback. We also
22 * need to pin the cache object to write back to.
23 */
24 int afs_set_page_dirty(struct page *page)
25 {
> 26 return fscache_set_page_dirty(page, afs_vnode_cache(AFS_FS_I(page->mapping->host)));
27 }
28
---
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: 34255 bytes --]
reply other threads:[~2021-10-13 0:11 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=202110130850.QpHC93Ek-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