From: kernel test robot <lkp@intel.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [rcu:dev.2020.12.15b 128/134] ERROR: modpost: "rcu_nocb_cpu_deoffload" undefined!
Date: Sun, 20 Dec 2020 01:37:07 +0800 [thread overview]
Message-ID: <202012200104.Q6vxFujD-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1176 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git dev.2020.12.15b
head: f895a17eec290b0038a6294d884a9cc92d7d6e80
commit: 892f898ac8cfffe89e3c7fd483c8eaf71b3f12aa [128/134] rcutorture: Test runtime toggling of CPUs' callback offloading
config: x86_64-rhel (attached as .config)
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git/commit/?id=892f898ac8cfffe89e3c7fd483c8eaf71b3f12aa
git remote add rcu https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git
git fetch --no-tags rcu dev.2020.12.15b
git checkout 892f898ac8cfffe89e3c7fd483c8eaf71b3f12aa
# save the attached .config to linux build tree
make W=1 ARCH=x86_64
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 >>, old ones prefixed by <<):
>> ERROR: modpost: "rcu_nocb_cpu_deoffload" [kernel/rcu/rcutorture.ko] undefined!
---
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: 45666 bytes --]
next reply other threads:[~2020-12-19 17:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-19 17:37 kernel test robot [this message]
2020-12-19 19:06 ` [rcu:dev.2020.12.15b 128/134] ERROR: modpost: "rcu_nocb_cpu_deoffload" undefined! Paul E. McKenney
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=202012200104.Q6vxFujD-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--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