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 58/69] fs/afs/write.c:27: undefined reference to `fscache_set_page_dirty'
Date: Thu, 22 Jul 2021 23:16:14 +0800 [thread overview]
Message-ID: <202107222310.Z1LZKp1d-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2077 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git fscache-iter-2
head: 589298a2e3fbae71f425089da4afb5a0fd3f939f
commit: a1b4b13a5a0037d49005930b50d186d71e07d74b [58/69] afs: Copy local writes to the cache when writing to the server
config: x86_64-randconfig-m001-20210722 (attached as .config)
compiler: gcc-10 (Ubuntu 10.3.0-1ubuntu1~20.04) 10.3.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/commit/?id=a1b4b13a5a0037d49005930b50d186d71e07d74b
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 a1b4b13a5a0037d49005930b50d186d71e07d74b
# 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:27: undefined reference to `fscache_set_page_dirty'
ld: fs/afs/write.o: in function `fscache_write_to_cache':
>> include/linux/fscache.h:557: undefined reference to `__fscache_write_to_cache'
ld: fs/afs/write.o: in function `fscache_clear_page_bits':
>> include/linux/fscache.h:547: undefined reference to `__fscache_clear_page_bits'
vim +27 fs/afs/write.c
17
18 static void afs_write_to_cache(struct afs_vnode *vnode, loff_t start, size_t len,
19 loff_t i_size);
20
21 /*
22 * Mark a page as having been made dirty and thus needing writeback. We also
23 * need to pin the cache object to write back to.
24 */
25 int afs_set_page_dirty(struct page *page)
26 {
> 27 return fscache_set_page_dirty(page, afs_vnode_cache(AFS_FS_I(page->mapping->host)));
28 }
29
---
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: 40248 bytes --]
reply other threads:[~2021-07-22 15:21 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=202107222310.Z1LZKp1d-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®