public inbox for [email protected]
 help / color / mirror / Atom feed
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 35/44] include/linux/instrumented.h:101: undefined reference to `fscache_n_updates'
Date: Sun, 24 Apr 2022 11:53:31 +0800	[thread overview]
Message-ID: <[email protected]> (raw)

tree:   https://github.com/ammarfaizi2/linux-block dhowells/linux-fs/netfs-maple
head:   931e50676c6598d0eda1954ead465519ff91874d
commit: f343507aeda88b2f1a528a659b8fadaa9b6b0f79 [35/44] netfs: Implement buffered writes through netfs_file_write_iter()
config: x86_64-rhel-8.3-func (https://download.01.org/0day-ci/archive/20220424/[email protected]/config)
compiler: gcc-11 (Debian 11.2.0-20) 11.2.0
reproduce (this is a W=1 build):
        # https://github.com/ammarfaizi2/linux-block/commit/f343507aeda88b2f1a528a659b8fadaa9b6b0f79
        git remote add ammarfaizi2-block https://github.com/ammarfaizi2/linux-block
        git fetch --no-tags ammarfaizi2-block dhowells/linux-fs/netfs-maple
        git checkout f343507aeda88b2f1a528a659b8fadaa9b6b0f79
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        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/buffered_write.o: in function `instrument_atomic_read_write':
>> include/linux/instrumented.h:101: undefined reference to `fscache_n_updates'
   ld: fs/netfs/buffered_write.o: in function `arch_atomic_inc':
>> arch/x86/include/asm/atomic.h:95: undefined reference to `fscache_n_updates'
   ld: fs/netfs/output.o: in function `fscache_begin_write_operation':
   include/linux/fscache.h:540: undefined reference to `__fscache_begin_write_operation'


vim +101 include/linux/instrumented.h

36e4d4dd4fc4f1 Marco Elver 2020-01-21   89  
00047c2e6d7c57 Marco Elver 2020-07-24   90  /**
00047c2e6d7c57 Marco Elver 2020-07-24   91   * instrument_atomic_read_write - instrument atomic read-write access
00047c2e6d7c57 Marco Elver 2020-07-24   92   *
00047c2e6d7c57 Marco Elver 2020-07-24   93   * Instrument an atomic read-write access. The instrumentation should be
00047c2e6d7c57 Marco Elver 2020-07-24   94   * inserted before the actual write happens.
00047c2e6d7c57 Marco Elver 2020-07-24   95   *
00047c2e6d7c57 Marco Elver 2020-07-24   96   * @ptr address of access
00047c2e6d7c57 Marco Elver 2020-07-24   97   * @size size of access
00047c2e6d7c57 Marco Elver 2020-07-24   98   */
00047c2e6d7c57 Marco Elver 2020-07-24   99  static __always_inline void instrument_atomic_read_write(const volatile void *v, size_t size)
00047c2e6d7c57 Marco Elver 2020-07-24  100  {
00047c2e6d7c57 Marco Elver 2020-07-24 @101  	kasan_check_write(v, size);
00047c2e6d7c57 Marco Elver 2020-07-24  102  	kcsan_check_atomic_read_write(v, size);
00047c2e6d7c57 Marco Elver 2020-07-24  103  }
00047c2e6d7c57 Marco Elver 2020-07-24  104  

:::::: The code at line 101 was first introduced by commit
:::::: 00047c2e6d7c576c1a847f7db07ef0fc58085f22 instrumented.h: Introduce read-write instrumentation hooks

:::::: TO: Marco Elver <[email protected]>
:::::: CC: Paul E. McKenney <[email protected]>

-- 
0-DAY CI Kernel Test Service
https://01.org/lkp

                 reply	other threads:[~2022-04-24  3:54 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