From: Pratyush Yadav <pratyush@kernel.org>
To: kernel test robot <oliver.sang@intel.com>
Cc: Mike Rapoport <rppt@kernel.org>, <oe-lkp@lists.linux.dev>,
<lkp@intel.com>, <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Alexander Graf <graf@amazon.com>,
Changyuan Lyu <changyuanl@google.com>,
Pasha Tatashin <pasha.tatashin@soleen.com>,
Pratyush Yadav <pratyush@kernel.org>,
Shuah Khan <shuah@kernel.org>, <kexec@lists.infradead.org>,
<linux-mm@kvack.org>
Subject: Re: [linus:master] [kho] b753522bed: INFO:trying_to_register_non-static_key
Date: Fri, 08 Aug 2025 13:28:31 +0200 [thread overview]
Message-ID: <mafs0sei2aw80.fsf@kernel.org> (raw)
In-Reply-To: <202508081032.1450e413-lkp@intel.com>
On Fri, Aug 08 2025, kernel test robot wrote:
> Hello,
>
[...]
>
>
> [ 59.011407][ T1] INFO: trying to register non-static key.
> [ 59.011783][ T1] The code is fine but needs lockdep annotation, or maybe
> [ 59.011783][ T1] you didn't initialize this object before use?
> [ 59.011783][ T1] turning off the locking correctness validator.
> [ 59.011783][ T1] CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Tainted: G T 6.16.0-rc5-00079-gb753522bed0b #1 PREEMPT(voluntary)
> [ 59.011783][ T1] Tainted: [T]=RANDSTRUCT
> [ 59.011783][ T1] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
> [ 59.011783][ T1] Call Trace:
Pasha, I think your patch [0] fixes this. Perhaps it is a good idea for
it to land independent of the LUO patches, since those are likely to
take some more time?
[0] https://lore.kernel.org/lkml/20250807014442.3829950-2-pasha.tatashin@soleen.com/
> [ 59.011783][ T1] <TASK>
> [ 59.011783][ T1] dump_stack_lvl (lib/dump_stack.c:123)
> [ 59.011783][ T1] assign_lock_key (kernel/locking/lockdep.c:988)
> [ 59.011783][ T1] register_lock_class (kernel/locking/lockdep.c:?)
> [ 59.011783][ T1] __lock_acquire (kernel/locking/lockdep.c:?)
> [ 59.011783][ T1] lock_acquire (kernel/locking/lockdep.c:5871)
> [ 59.011783][ T1] ? xa_load_or_alloc (include/linux/xarray.h:699 kernel/kexec_handover.c:106)
> [ 59.011783][ T1] ? tracer_preempt_off (kernel/trace/trace_irqsoff.c:412)
> [ 59.011783][ T1] _raw_spin_lock (include/linux/spinlock_api_smp.h:133 kernel/locking/spinlock.c:154)
> [ 59.011783][ T1] ? xa_load_or_alloc (include/linux/xarray.h:699 kernel/kexec_handover.c:106)
> [ 59.011783][ T1] xa_load_or_alloc (include/linux/xarray.h:699 kernel/kexec_handover.c:106)
> [ 59.011783][ T1] __kho_preserve_order (kernel/kexec_handover.c:156)
> [ 59.011783][ T1] kho_test_init (lib/test_kho.c:84)
> [ 59.011783][ T1] ? __cfi_kho_test_init (lib/test_kho.c:271)
> [ 59.011783][ T1] do_one_initcall (init/main.c:1274)
> [ 59.011783][ T1] ? __cfi_kho_test_init (lib/test_kho.c:271)
> [ 59.011783][ T1] ? kasan_save_track (arch/x86/include/asm/current.h:25 mm/kasan/common.c:60 mm/kasan/common.c:69)
> [ 59.011783][ T1] ? kasan_save_track (mm/kasan/common.c:48 mm/kasan/common.c:68)
> [ 59.011783][ T1] ? __kasan_kmalloc (mm/kasan/common.c:398)
> [ 59.011783][ T1] ? tracer_hardirqs_off (kernel/trace/trace_irqsoff.c:412)
> [ 59.011783][ T1] ? do_initcalls (include/linux/slab.h:909 include/linux/slab.h:1039 init/main.c:1345)
> [ 59.011783][ T1] ? kernel_init_freeable (init/main.c:1588)
> [ 59.011783][ T1] ? tracer_hardirqs_on (kernel/trace/trace_irqsoff.c:452)
> [ 59.011783][ T1] ? tracer_hardirqs_off (kernel/trace/trace_irqsoff.c:412)
> [ 59.011783][ T1] ? tracer_hardirqs_on (kernel/trace/trace_irqsoff.c:452)
> [ 59.011783][ T1] ? irqentry_exit (kernel/entry/common.c:311)
> [ 59.011783][ T1] ? next_arg (lib/cmdline.c:273)
> [ 59.011783][ T1] ? parameq (kernel/params.c:91)
> [ 59.011783][ T1] ? parse_args (kernel/params.c:?)
> [ 59.011783][ T1] do_initcall_level (init/main.c:1335)
> [ 59.011783][ T1] do_initcalls (init/main.c:1349)
> [ 59.011783][ T1] kernel_init_freeable (init/main.c:1588)
> [ 59.011783][ T1] ? __cfi_kernel_init (init/main.c:1466)
> [ 59.011783][ T1] kernel_init (init/main.c:1476)
> [ 59.011783][ T1] ? __cfi_kernel_init (init/main.c:1466)
> [ 59.011783][ T1] ret_from_fork (arch/x86/kernel/process.c:154)
> [ 59.011783][ T1] ? __cfi_kernel_init (init/main.c:1466)
> [ 59.011783][ T1] ret_from_fork_asm (arch/x86/entry/entry_64.S:255)
> [ 59.011783][ T1] </TASK>
--
Regards,
Pratyush Yadav
prev parent reply other threads:[~2025-08-08 12:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-08 8:45 [linus:master] [kho] b753522bed: INFO:trying_to_register_non-static_key kernel test robot
2025-08-08 11:28 ` Pratyush Yadav [this message]
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=mafs0sei2aw80.fsf@kernel.org \
--to=pratyush@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=changyuanl@google.com \
--cc=graf@amazon.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
--cc=pasha.tatashin@soleen.com \
--cc=rppt@kernel.org \
--cc=shuah@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.