From: kernel test robot <[email protected]>
To: David Howells <[email protected]>
Cc: [email protected],
GNU/Weeb Mailing List <[email protected]>,
[email protected]
Subject: [ammarfaizi2-block:dhowells/linux-fs/netfs-maple 24/40] include/linux/fscache.h:540: undefined reference to `__fscache_begin_write_operation'
Date: Tue, 5 Apr 2022 23:28:10 +0800 [thread overview]
Message-ID: <[email protected]> (raw)
tree: https://github.com/ammarfaizi2/linux-block dhowells/linux-fs/netfs-maple
head: 674eea41fc70a740ff83ec590f9833f805852464
commit: d77af6a0e73b5e3c4bae01c64df536f2662e2dab [24/40] netfs: Dispatch write requests to process a writeback slice
config: x86_64-rhel-8.3-func (https://download.01.org/0day-ci/archive/20220405/[email protected]/config)
compiler: gcc-11 (Debian 11.2.0-19) 11.2.0
reproduce (this is a W=1 build):
# https://github.com/ammarfaizi2/linux-block/commit/d77af6a0e73b5e3c4bae01c64df536f2662e2dab
git remote add ammarfaizi2-block https://github.com/ammarfaizi2/linux-block
git fetch --no-tags ammarfaizi2-block dhowells/linux-fs/netfs-maple
git checkout d77af6a0e73b5e3c4bae01c64df536f2662e2dab
# save the config file 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 <[email protected]>
All errors (new ones prefixed by >>):
ld: fs/netfs/output.o: in function `fscache_begin_write_operation':
>> include/linux/fscache.h:540: undefined reference to `__fscache_begin_write_operation'
vim +540 include/linux/fscache.h
9af1c6c3089b29 David Howells 2021-10-20 516
16f2f4e679cfda David Howells 2021-08-27 517 /**
16f2f4e679cfda David Howells 2021-08-27 518 * fscache_begin_write_operation - Begin a write operation for the netfs lib
16f2f4e679cfda David Howells 2021-08-27 519 * @cres: The cache resources for the write being performed
16f2f4e679cfda David Howells 2021-08-27 520 * @cookie: The cookie representing the cache object
16f2f4e679cfda David Howells 2021-08-27 521 *
16f2f4e679cfda David Howells 2021-08-27 522 * Begin a write operation on behalf of the netfs helper library. @cres
16f2f4e679cfda David Howells 2021-08-27 523 * indicates the cache resources to which the operation state should be
16f2f4e679cfda David Howells 2021-08-27 524 * attached; @cookie indicates the cache object that will be accessed.
16f2f4e679cfda David Howells 2021-08-27 525 *
16f2f4e679cfda David Howells 2021-08-27 526 * @cres->inval_counter is set from @cookie->inval_counter for comparison at
16f2f4e679cfda David Howells 2021-08-27 527 * the end of the operation. This allows invalidation during the operation to
16f2f4e679cfda David Howells 2021-08-27 528 * be detected by the caller.
16f2f4e679cfda David Howells 2021-08-27 529 *
16f2f4e679cfda David Howells 2021-08-27 530 * Returns:
16f2f4e679cfda David Howells 2021-08-27 531 * * 0 - Success
16f2f4e679cfda David Howells 2021-08-27 532 * * -ENOBUFS - No caching available
16f2f4e679cfda David Howells 2021-08-27 533 * * Other error code from the cache, such as -ENOMEM.
16f2f4e679cfda David Howells 2021-08-27 534 */
16f2f4e679cfda David Howells 2021-08-27 535 static inline
16f2f4e679cfda David Howells 2021-08-27 536 int fscache_begin_write_operation(struct netfs_cache_resources *cres,
16f2f4e679cfda David Howells 2021-08-27 537 struct fscache_cookie *cookie)
16f2f4e679cfda David Howells 2021-08-27 538 {
16f2f4e679cfda David Howells 2021-08-27 539 if (fscache_cookie_enabled(cookie))
16f2f4e679cfda David Howells 2021-08-27 @540 return __fscache_begin_write_operation(cres, cookie);
16f2f4e679cfda David Howells 2021-08-27 541 return -ENOBUFS;
16f2f4e679cfda David Howells 2021-08-27 542 }
16f2f4e679cfda David Howells 2021-08-27 543
:::::: The code at line 540 was first introduced by commit
:::::: 16f2f4e679cfdaa9552574484f104014908a76c6 nfs: Implement cache I/O by accessing the cache directly
:::::: TO: David Howells <[email protected]>
:::::: CC: David Howells <[email protected]>
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-04-05 15:28 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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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