From: kernel test robot <[email protected]>
To: "Paul E. McKenney" <[email protected]>
Cc: [email protected],
GNU/Weeb Mailing List <[email protected]>,
[email protected]
Subject: [ammarfaizi2-block:paulmck/linux-rcu/for-peterz.2022.05.25a 54/62] ERROR: modpost: "rcu_trc_cmpxchg_need_qs" [kernel/torture.ko] undefined!
Date: Thu, 26 May 2022 03:45:01 +0800 [thread overview]
Message-ID: <[email protected]> (raw)
tree: https://github.com/ammarfaizi2/linux-block paulmck/linux-rcu/for-peterz.2022.05.25a
head: 4b2a6af8fe31e85fb2754b8da5072041a4dea471
commit: 0f7cb0c989a98c0d1e758e265021514bc6b595c0 [54/62] rcu-tasks: Atomically update .b.need_qs to obviate count
config: x86_64-randconfig-a011 (https://download.01.org/0day-ci/archive/20220526/[email protected]/config)
compiler: gcc-11 (Debian 11.3.0-1) 11.3.0
reproduce (this is a W=1 build):
# https://github.com/ammarfaizi2/linux-block/commit/0f7cb0c989a98c0d1e758e265021514bc6b595c0
git remote add ammarfaizi2-block https://github.com/ammarfaizi2/linux-block
git fetch --no-tags ammarfaizi2-block paulmck/linux-rcu/for-peterz.2022.05.25a
git checkout 0f7cb0c989a98c0d1e758e265021514bc6b595c0
# 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 where applicable
Reported-by: kernel test robot <[email protected]>
All error/warnings (new ones prefixed by >>, old ones prefixed by <<):
In file included from kernel/rcu/update.c:606:
kernel/rcu/tasks.h: In function 'rcu_trc_cmpxchg_need_qs':
>> kernel/rcu/tasks.h:1233:27: warning: variable 'trs_new' set but not used [-Wunused-but-set-variable]
1233 | union rcu_special trs_new = trs_old;
| ^~~~~~~
--
>> ERROR: modpost: "rcu_trc_cmpxchg_need_qs" [kernel/torture.ko] undefined!
>> ERROR: modpost: "rcu_trc_cmpxchg_need_qs" [kernel/rcu/rcuscale.ko] undefined!
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-05-25 19:45 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