linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <oliver.sang@intel.com>
To: Asier Gutierrez <gutierrez.asier@huawei-partners.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
	<damon@lists.linux.dev>, <linux-mm@kvack.org>,
	<gutierrez.asier@huawei-partners.com>, <sj@kernel.org>,
	<akpm@linux-foundation.org>, <linux-kernel@vger.kernel.org>,
	<wangkefeng.wang@huawei.com>, <artem.kuzin@huawei.com>,
	<stepanov.anatoly@huawei.com>, <oliver.sang@intel.com>
Subject: Re: [RFC PATCH v1] mm: improve call_controls_lock
Date: Tue, 6 Jan 2026 14:41:24 +0800	[thread overview]
Message-ID: <202601061219.9effe621-lkp@intel.com> (raw)
In-Reply-To: <20251229145533.2437293-1-gutierrez.asier@huawei-partners.com>



Hello,

kernel test robot noticed "INFO:trying_to_register_non-static_key" on:

commit: d87e70902c77a5dc3a4fd4fe78c1172b4b644495 ("[RFC PATCH v1] mm: improve call_controls_lock")
url: https://github.com/intel-lab-lkp/linux/commits/Asier-Gutierrez/mm-improve-call_controls_lock/20251229-225805
base: v6.19-rc3
patch link: https://lore.kernel.org/all/20251229145533.2437293-1-gutierrez.asier@huawei-partners.com/
patch subject: [RFC PATCH v1] mm: improve call_controls_lock

in testcase: boot

config: i386-randconfig-005-20260101
compiler: gcc-14
test machine: qemu-system-i386 -enable-kvm -cpu SandyBridge -smp 2 -m 4G

(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/202601061219.9effe621-lkp@intel.com


[    1.225255][    T1] INFO: trying to register non-static key.
[    1.226642][    T1] The code is fine but needs lockdep annotation, or maybe
[    1.227181][    T1] you didn't initialize this object before use?
[    1.227181][    T1] turning off the locking correctness validator.
[    1.227181][    T1] CPU: 1 UID: 0 PID: 1 Comm: swapper/0 Tainted: G                T   6.19.0-rc3-00001-gd87e70902c77 #1 VOLUNTARY  7c12528289a79a90bef93a94128a85da378fc562
[    1.227181][    T1] Tainted: [T]=RANDSTRUCT
[    1.227181][    T1] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
[    1.227181][    T1] Call Trace:
[    1.227181][    T1]  ? dump_stack_lvl (lib/dump_stack.c:122)
[    1.227181][    T1]  ? dump_stack (lib/dump_stack.c:130)
[    1.227181][    T1]  ? register_lock_class (kernel/locking/lockdep.c:985 kernel/locking/lockdep.c:1299)
[    1.227181][    T1]  ? sched_clock_noinstr (arch/x86/kernel/tsc.c:273)
[    1.227181][    T1]  ? damon_start (mm/damon/core.c:1372)
[    1.227181][    T1]  ? kvm_sched_clock_read (arch/x86/kernel/kvmclock.c:91 (discriminator 2))
[    1.227181][    T1]  ? __lock_acquire (kernel/locking/lockdep.c:5113)
[    1.227181][    T1]  ? lock_acquire (kernel/locking/lockdep.c:470 (discriminator 4) kernel/locking/lockdep.c:5870 (discriminator 4))
[    1.227181][    T1]  ? damon_call (mm/damon/core.c:1460)
[    1.227181][    T1]  ? damon_start (mm/damon/core.c:1372)
[    1.227181][    T1]  ? __mutex_unlock_slowpath (arch/x86/include/asm/atomic.h:23 include/linux/atomic/atomic-arch-fallback.h:457 include/linux/atomic/atomic-long.h:40 include/linux/atomic/atomic-instrumented.h:3189 kernel/locking/mutex.c:947)
[    1.227181][    T1]  ? hrtimer_nanosleep_restart (kernel/time/sleep_timeout.c:62)
[    1.227181][    T1]  ? _raw_spin_lock (include/linux/spinlock_api_smp.h:134 kernel/locking/spinlock.c:154)
[    1.227181][    T1]  ? damon_call (mm/damon/core.c:1460)
[    1.227181][    T1]  ? damon_stat_start (mm/damon/stat.c:219)
[    1.227181][    T1]  ? damon_reclaim_init (mm/damon/stat.c:258)
[    1.227181][    T1]  ? damon_stat_init (mm/damon/stat.c:271)
[    1.227181][    T1]  ? do_one_initcall (init/main.c:1378)
[    1.227181][    T1]  ? do_initcalls (init/main.c:1439 (discriminator 3) init/main.c:1456 (discriminator 3))
[    1.227181][    T1]  ? kernel_init_freeable (init/main.c:1692)
[    1.227181][    T1]  ? rest_init (init/main.c:1570)
[    1.227181][    T1]  ? kernel_init (init/main.c:1580)
[    1.227181][    T1]  ? ret_from_fork (arch/x86/kernel/process.c:164)
[    1.227181][    T1]  ? rest_init (init/main.c:1570)
[    1.227181][    T1]  ? ret_from_fork_asm (arch/x86/entry/entry_32.S:737)
[    1.227181][    T1]  ? entry_INT80_32 (arch/x86/entry/entry_32.S:945)


The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20260106/202601061219.9effe621-lkp@intel.com



-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki



      parent reply	other threads:[~2026-01-06  6:41 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-29 14:55 Asier Gutierrez
2025-12-29 15:22 ` SeongJae Park
2025-12-30  9:02   ` Gutierrez Asier
2025-12-31  5:01     ` SeongJae Park
2025-12-31  2:15   ` JaeJoon Jung
2025-12-31  4:59     ` SeongJae Park
2025-12-31  6:10       ` JaeJoon Jung
2025-12-31  7:51         ` JaeJoon Jung
2025-12-31 15:32         ` SeongJae Park
2026-01-01  1:11           ` JaeJoon Jung
2026-01-01  2:00             ` SeongJae Park
2026-01-01  2:34               ` JaeJoon Jung
2026-01-01 22:44                 ` SeongJae Park
2026-01-01  1:07       ` JaeJoon Jung
2026-01-01  1:51         ` SeongJae Park
2026-01-01  2:29           ` JaeJoon Jung
2026-01-06  6:41 ` kernel test robot [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=202601061219.9effe621-lkp@intel.com \
    --to=oliver.sang@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=artem.kuzin@huawei.com \
    --cc=damon@lists.linux.dev \
    --cc=gutierrez.asier@huawei-partners.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=oe-lkp@lists.linux.dev \
    --cc=sj@kernel.org \
    --cc=stepanov.anatoly@huawei.com \
    --cc=wangkefeng.wang@huawei.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