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/75] include/linux/fscache.h:547: undefined reference to `__fscache_clear_page_bits'
Date: Fri, 10 Sep 2021 08:46:51 +0800 [thread overview]
Message-ID: <202109100835.5uVRyokc-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3632 bytes --]
Hi David,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git fscache-iter-2
head: 7c7521adffeb04466a42e8e1956353b9d9038d02
commit: a1b4b13a5a0037d49005930b50d186d71e07d74b [58/75] afs: Copy local writes to the cache when writing to the server
config: x86_64-randconfig-a001-20210908 (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=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 `fscache_clear_page_bits':
>> include/linux/fscache.h:547: undefined reference to `__fscache_clear_page_bits'
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 `afs_set_page_dirty':
>> fs/afs/write.c:27: undefined reference to `fscache_set_page_dirty'
vim +547 include/linux/fscache.h
94d30ae90a00ca David Howells 2013-09-21 542
e29afe6f941d92 David Howells 2020-09-22 543 static inline void fscache_clear_page_bits(struct address_space *mapping,
e29afe6f941d92 David Howells 2020-09-22 544 loff_t start, size_t len)
e29afe6f941d92 David Howells 2020-09-22 545 {
e29afe6f941d92 David Howells 2020-09-22 546 if (fscache_available())
e29afe6f941d92 David Howells 2020-09-22 @547 __fscache_clear_page_bits(mapping, start, len);
e29afe6f941d92 David Howells 2020-09-22 548 }
e29afe6f941d92 David Howells 2020-09-22 549
e29afe6f941d92 David Howells 2020-09-22 550 static inline void fscache_write_to_cache(struct fscache_cookie *cookie,
e29afe6f941d92 David Howells 2020-09-22 551 struct address_space *mapping,
e29afe6f941d92 David Howells 2020-09-22 552 loff_t start, size_t len, loff_t i_size,
e29afe6f941d92 David Howells 2020-09-22 553 netfs_io_terminated_t term_func,
e29afe6f941d92 David Howells 2020-09-22 554 void *term_func_priv)
e29afe6f941d92 David Howells 2020-09-22 555 {
e29afe6f941d92 David Howells 2020-09-22 556 if (fscache_available()) {
e29afe6f941d92 David Howells 2020-09-22 @557 __fscache_write_to_cache(cookie, mapping, start, len, i_size,
e29afe6f941d92 David Howells 2020-09-22 558 term_func, term_func_priv);
e29afe6f941d92 David Howells 2020-09-22 559 } else {
e29afe6f941d92 David Howells 2020-09-22 560 fscache_clear_page_bits(mapping, start, len);
e29afe6f941d92 David Howells 2020-09-22 561 if (term_func)
e29afe6f941d92 David Howells 2020-09-22 562 term_func(term_func_priv, -ENOBUFS, false);
e29afe6f941d92 David Howells 2020-09-22 563 }
e29afe6f941d92 David Howells 2020-09-22 564
:::::: The code at line 547 was first introduced by commit
:::::: e29afe6f941d92e05bfaf15c9fcb4fbc4760244f fscache: Add support for writing to the cache
:::::: TO: David Howells <dhowells@redhat.com>
:::::: CC: David Howells <dhowells@redhat.com>
---
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: 31906 bytes --]
reply other threads:[~2021-09-10 1:06 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=202109100835.5uVRyokc-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
Powered by JetHome