From: kernel test robot <lkp@intel.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: [paulmck-rcu:dev.2025.11.13a 25/27] ERROR: modpost: "tasklist_lock" [kernel/rcu/rcutorture.ko] undefined!
Date: Tue, 18 Nov 2025 11:02:47 +0800 [thread overview]
Message-ID: <202511181007.iHxSV1IG-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git dev.2025.11.13a
head: 38cc1fc7cc9d7c9ed5275c1e78256431da7721c5
commit: 8b6753ddeaa69d04d6ff8b3bee0bf81a0607d396 [25/27] rcutorture: Add a textbook-style trivial preemptible RCU
config: x86_64-randconfig-101-20251118 (https://download.01.org/0day-ci/archive/20251118/202511181007.iHxSV1IG-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251118/202511181007.iHxSV1IG-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/202511181007.iHxSV1IG-lkp@intel.com/
All errors (new ones prefixed by >>, old ones prefixed by <<):
>> ERROR: modpost: "tasklist_lock" [kernel/rcu/rcutorture.ko] undefined!
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2025-11-18 3:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-18 3:02 kernel test robot [this message]
2025-11-18 19:31 ` [paulmck-rcu:dev.2025.11.13a 25/27] ERROR: modpost: "tasklist_lock" [kernel/rcu/rcutorture.ko] 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=202511181007.iHxSV1IG-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-kernel@vger.kernel.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