From: kernel test robot <lkp@intel.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 10381/10451] kernel/rcu/rcu.h:138:undefined reference to `csd_lock_is_stuck'
Date: Wed, 3 Jul 2024 19:17:26 +0800 [thread overview]
Message-ID: <202407031919.QUBn1G5D-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 0b58e108042b0ed28a71cd7edf5175999955b233
commit: eb52b064da252ef2ecc1fd112ebd3f687f9affd5 [10381/10451] Merge branch 'non-rcu/next' of git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git
config: riscv-randconfig-r133-20240211 (https://download.01.org/0day-ci/archive/20240703/202407031919.QUBn1G5D-lkp@intel.com/config)
compiler: riscv64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240703/202407031919.QUBn1G5D-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202407031919.QUBn1G5D-lkp@intel.com/
All errors (new ones prefixed by >>):
riscv64-linux-ld: kernel/rcu/tree.o: in function `sync_rcu_exp_done':
kernel/rcu/tree_exp.h:155:(.text+0xd0c): undefined reference to `csd_lock_is_stuck'
riscv64-linux-ld: kernel/rcu/tree.o: in function `rcu_seq_current':
>> kernel/rcu/rcu.h:138:(.text+0x3222): undefined reference to `csd_lock_is_stuck'
vim +138 kernel/rcu/rcu.h
2e8c28c2dd96c6 Paul E. McKenney 2017-02-20 134
8660b7d8a54522 Paul E. McKenney 2017-03-13 135 /* Return the current value the update side's sequence number, no ordering. */
8660b7d8a54522 Paul E. McKenney 2017-03-13 136 static inline unsigned long rcu_seq_current(unsigned long *sp)
8660b7d8a54522 Paul E. McKenney 2017-03-13 137 {
8660b7d8a54522 Paul E. McKenney 2017-03-13 @138 return READ_ONCE(*sp);
8660b7d8a54522 Paul E. McKenney 2017-03-13 139 }
8660b7d8a54522 Paul E. McKenney 2017-03-13 140
:::::: The code at line 138 was first introduced by commit
:::::: 8660b7d8a545227fd9ee80508aa82528ea9947d7 srcu: Use rcu_segcblist to track SRCU callbacks
:::::: TO: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
:::::: CC: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-07-03 11:18 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=202407031919.QUBn1G5D-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=paulmck@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