From: kernel test robot <yi1.lai@intel.com>
To: Yury Norov <ynorov@nvidia.com>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com,
linux-kernel@vger.kernel.org,
Eliot Courtney <ecourtney@nvidia.com>,
linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
yi1.lai@intel.com
Subject: [linus:master] [lib] f4806cc63c: INFO:trying_to_register_non-static_key
Date: Thu, 10 Sep 2026 11:29:18 +0800 [thread overview]
Message-ID: <202609101106.771b567e-lkp@intel.com> (raw)
Hello,
kernel test robot noticed "INFO:trying_to_register_non-static_key" on:
commit: f4806cc63cc65bd752fd72d84937614dca6504ec ("lib: test bitmap vs IDA vs Maple Tree performance for region allocations") https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
[test failed on linux-next/master a9d7ced84989ec05be09b4b8428759ef60450a0f]
in testcase: boot
config: i386-randconfig-054-20260822
compiler: gcc-14
test machine: qemu-system-i386 -enable-kvm -cpu SandyBridge -smp 2 -m 4G
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 <yi1.lai@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202609101106.771b567e-lkp@intel.com
[ 157.121248][ T1] INFO: trying to register non-static key.
[ 157.122147][ T1] The code is fine but needs lockdep annotation, or maybe
[ 157.122147][ T1] you didn't initialize this object before use?
[ 157.122147][ T1] turning off the locking correctness validator.
[ 157.122147][ T1] CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Not tainted 7.2.0-rc4-00086-gf4806cc63cc6 #1 PREEMPT(full) 167be1ded5cf2d764b5931072317f04af057210f
[ 157.122147][ T1] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
[ 157.122147][ T1] Call Trace:
[ 157.122147][ T1] ? show_stack (x86/kernel/dumpstack.c:319 x86/kernel/dumpstack.c:337)
[ 157.122147][ T1] ? dump_stack_lvl (dump_stack.c:94 dump_stack.c:120)
[ 157.122147][ T1] ? dump_stack (dump_stack.c:129)
[ 157.122147][ T1] ? register_lock_class (locking/lockdep.c:984 locking/lockdep.c:1299)
[ 157.122147][ T1] ? __lock_acquire (locking/lockdep.c:5237)
[ 157.122147][ T1] ? __lock_acquire (locking/lockdep.c:5112)
[ 157.122147][ T1] ? lock_acquire (locking/lockdep.c:5872)
[ 157.122147][ T1] ? mtree_alloc_range (linux/spinlock.h:342 maple_tree.c:5800)
[ 157.122147][ T1] ? __lock_acquire (locking/lockdep.c:5237)
[ 157.122147][ T1] ? lock_acquire (locking/lockdep.c:5833)
[ 157.122147][ T1] ? mtree_alloc_range (linux/spinlock.h:342 maple_tree.c:5800)
[ 157.122147][ T1] ? _raw_spin_lock (linux/spinlock_api_smp.h:158 (discriminator 1) locking/spinlock.c:158 (discriminator 1))
[ 157.122147][ T1] ? mtree_alloc_range (linux/spinlock.h:342 maple_tree.c:5800)
[ 157.122147][ T1] ? __lock_release+0x42/0x140
[ 157.122147][ T1] ? kvm_clock_get_cycles (x86/kernel/kvmclock.c:80 (discriminator 1) x86/kernel/kvmclock.c:87 (discriminator 1))
[ 157.122147][ T1] ? ktime_get (time/timekeeping.c:321 time/timekeeping.c:455 time/timekeeping.c:973)
[ 157.122147][ T1] ? vprintk_default (printk/printk.c:2494)
[ 157.122147][ T1] ? benchmark_maple_tree (region_alloc_benchmark.c:136 (discriminator 1))
[ 157.122147][ T1] ? region_alloc_benchmark (region_alloc_benchmark.c:197 (discriminator 1))
[ 157.122147][ T1] ? benchmark_ida (region_alloc_benchmark.c:124)
[ 157.122147][ T1] ? do_one_initcall (main.c:1347)
[ 157.122147][ T1] ? do_initcalls (main.c:1409 (discriminator 1) main.c:1425 (discriminator 1))
[ 157.122147][ T1] ? kernel_init_freeable (main.c:1445 main.c:1658)
[ 157.122147][ T1] ? rest_init (main.c:717)
[ 157.122147][ T1] ? kernel_init (main.c:1548)
[ 157.122147][ T1] ? ret_from_fork (x86/kernel/process.c:158)
[ 157.122147][ T1] ? rest_init (main.c:717)
[ 157.122147][ T1] ? ret_from_fork_asm (x86/entry/entry_32.S:736)
[ 157.122147][ T1] ? entry_INT80_32 (x86/entry/entry_32.S:940)
[ 158.731005][ C0] clocksource: Marking clocksource tsc unstable due to frequency skew
[ 158.804793][ C0] clocksource: Watchdog kvm-clock interval: 63117ns
[ 158.871025][ C0] clocksource: Clocksource tsc interval: 62703ns
[ 158.935843][ C0] tsc: Marking TSC unstable due to clocksource watchdog
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20260910/202609101106.771b567e-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-09-10 3:29 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=202609101106.771b567e-lkp@intel.com \
--to=yi1.lai@intel.com \
--cc=ecourtney@nvidia.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=ynorov@nvidia.com \
/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