From: kernel test robot <oliver.sang@intel.com>
To: Yury Norov <ynorov@nvidia.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
Eliot Courtney <ecourtney@nvidia.com>,
<linux-kernel@vger.kernel.org>, <oliver.sang@intel.com>
Subject: [linux-next:master] [lib] f4806cc63c: INFO:trying_to_register_non-static_key
Date: Wed, 12 Aug 2026 15:37:25 +0800 [thread overview]
Message-ID: <202608121556.f0a5b5ad-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/next/linux-next.git master
[test failed on linux-next/master 415606a7be939835db9b0d6b711887586646346d]
in testcase: trinity
version:
with following parameters:
runtime: 300s
group: group-04
nr_groups: 5
config: x86_64-randconfig-r071-20260801
compiler: gcc-12
test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 32G
(please refer to attached dmesg/kmsg for entire log/backtrace)
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 <oliver.sang@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202608121556.f0a5b5ad-lkp@intel.com
[ 17.750298][ T1] INFO: trying to register non-static key.
[ 17.752032][ T1] The code is fine but needs lockdep annotation, or maybe
[ 17.752032][ T1] you didn't initialize this object before use?
[ 17.752032][ T1] turning off the locking correctness validator.
[ 17.752032][ T1] CPU: 1 UID: 0 PID: 1 Comm: swapper/0 Not tainted 7.2.0-rc4-00086-gf4806cc63cc6 #1 PREEMPT(full)
[ 17.752032][ T1] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
[ 17.752032][ T1] Call Trace:
[ 17.752032][ T1] <TASK>
[ 17.752032][ T1] dump_stack_lvl (dump_stack.c:94 dump_stack.c:120)
[ 17.752032][ T1] register_lock_class (locking/lockdep.c:1332)
[ 17.752032][ T1] ? __lock_release+0x53/0x10d
[ 17.752032][ T1] ? mtree_alloc_range (linux/spinlock.h:342 maple_tree.c:5800)
[ 17.752032][ T1] __lock_acquire (locking/lockdep.c:5112)
[ 17.752032][ T1] ? mtree_alloc_range (linux/spinlock.h:342 maple_tree.c:5800)
[ 17.752032][ T1] lock_acquire (trace/events/lock.h:23 locking/lockdep.c:5831)
[ 17.752032][ T1] ? mtree_alloc_range (linux/spinlock.h:342 maple_tree.c:5800)
[ 17.752032][ T1] ? lock_acquire (trace/events/lock.h:23 locking/lockdep.c:5831)
[ 17.752032][ T1] _raw_spin_lock (linux/spinlock_api_smp.h:158 locking/spinlock.c:158)
[ 17.752032][ T1] ? mtree_alloc_range (linux/spinlock.h:342 maple_tree.c:5800)
[ 17.752032][ T1] mtree_alloc_range (linux/spinlock.h:342 maple_tree.c:5800)
[ 17.752032][ T1] ? mtree_insert (maple_tree.c:5783)
[ 17.752032][ T1] ? kvm_clock_read (x86/kernel/kvmclock.c:80)
[ 17.752032][ T1] benchmark_maple_tree (region_alloc_benchmark.c:136)
[ 17.752032][ T1] ? benchmark_bitmap (region_alloc_benchmark.c:58 (discriminator 3))
[ 17.752032][ T1] ? _printk (printk/printk.c:2504)
[ 17.752032][ T1] ? benchmark_bitmap (region_alloc_benchmark.c:54 (discriminator 3))
[ 17.752032][ T1] region_alloc_benchmark (region_alloc_benchmark.c:197)
[ 17.752032][ T1] ? bfq_init (bfq-iosched.c:7649)
[ 17.752032][ T1] ? benchmark_ida (region_alloc_benchmark.c:124)
[ 17.752032][ T1] do_one_initcall (main.c:1347)
[ 17.752032][ T1] ? rcu_lock_acquire (linux/rcupdate.h:960)
[ 17.752032][ T1] ? __kmalloc_noprof (slub.c:5363 slub.c:5387)
[ 17.752032][ T1] ? do_initcalls (linux/slab.h:973 linux/slab.h:1290 main.c:1418)
[ 17.752032][ T1] do_initcalls (main.c:1409 main.c:1425)
[ 17.752032][ T1] kernel_init_freeable (main.c:1445 main.c:1658)
[ 17.752032][ T1] ? rest_init (main.c:717)
[ 17.752032][ T1] kernel_init (main.c:1548)
[ 17.752032][ T1] ret_from_fork (x86/kernel/process.c:158)
[ 17.752032][ T1] ? arch_exit_to_user_mode_prepare+0x74/0x74
[ 17.752032][ T1] ? rest_init (main.c:717)
[ 17.752032][ T1] ret_from_fork_asm (x86/entry/entry_64.S:245)
[ 17.752032][ T1] </TASK>
[ 24.013548][ T1] Maple 3779202887 2484049644 60575 1000000 1550928
[ 24.990890][ T1] IDA 575247255 396825927 60575 1000000 134928
[ 25.327943][ T1] Bitmap 8349201 80133 6156 100000 12504
[ 25.366002][ T29] Freeing initrd memory: 118776K
[ 25.842057][ T1] Maple 293091941 215862643 6156 100000 157776
[ 25.941163][ T1] IDA 59238562 34683461 6156 100000 14352
[ 25.989651][ T1] Bitmap 109541 8255 612 10000 1256
[ 26.030185][ T1] Maple 19150121 16184256 612 10000 15952
[ 26.042611][ T1] IDA 4157285 3069915 612 10000 1936
[ 26.054183][ T1] Bitmap 7207 1471 55 1000 128
[ 26.066923][ T1] Maple 1873335 1797272 55 1000 1616
[ 26.075720][ T1] IDA 680707 581315 55 1000 208
[ 26.082353][ T1] Bitmap 2691 523 22 100 16
[ 26.087980][ T1] Maple 177500 187648 22 100 848
[ 26.093213][ T1] IDA 62046 36889 22 100 208
[ 26.098353][ T1] Bitmap 1028 314 10 10 8
[ 26.103600][ T1] Maple 49537 47114 10 10 336
[ 26.108703][ T1] IDA 6863 4643 10 10 80
[ 26.113754][ T1] Region allocation benchmark complete
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20260812/202608121556.f0a5b5ad-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-08-12 7:37 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=202608121556.f0a5b5ad-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=ecourtney@nvidia.com \
--cc=linux-kernel@vger.kernel.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