From: kernel test robot <oliver.sang@intel.com>
To: Jarkko Sakkinen <jarkko@kernel.org>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>, <oliver.sang@intel.com>
Subject: [jarkko-tpmdd:keys-graveyard] [keys] aa52a1fbfc: WARNING:inconsistent_lock_state
Date: Mon, 31 Mar 2025 22:37:22 +0800 [thread overview]
Message-ID: <202503312252.bef52733-lkp@intel.com> (raw)
Hello,
kernel test robot noticed "WARNING:inconsistent_lock_state" on:
commit: aa52a1fbfc9a9fcfe467c256dc2d91d8333db80e ("keys: Add a list for unreferenced keys")
https://git.kernel.org/cgit/linux/kernel/git/jarkko/linux-tpmdd.git keys-graveyard
in testcase: boot
config: i386-randconfig-141-20250330
compiler: gcc-12
test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 16G
(please refer to attached dmesg/kmsg for entire log/backtrace)
+-------------------------------------------------+------------+------------+
| | 980a573621 | aa52a1fbfc |
+-------------------------------------------------+------------+------------+
| WARNING:inconsistent_lock_state | 0 | 21 |
| inconsistent{SOFTIRQ-ON-W}->{IN-SOFTIRQ-W}usage | 0 | 21 |
+-------------------------------------------------+------------+------------+
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/202503312252.bef52733-lkp@intel.com
[ 10.186009][ C0] WARNING: inconsistent lock state
[ 10.186875][ C0] 6.14.0-05893-gaa52a1fbfc9a #1 Tainted: G T
[ 10.188003][ C0] --------------------------------
[ 10.188912][ C0] inconsistent {SOFTIRQ-ON-W} -> {IN-SOFTIRQ-W} usage.
[ 10.189954][ C0] ksoftirqd/0/14 [HC0[0]:SC1[1]:HE1:SE0] takes:
[ 10.190715][ C0] 432b47f0 (key_serial_lock){+.?.}-{3:3}, at: key_put (security/keys/key.c:663 security/keys/key.c:647)
[ 10.191504][ C0] {SOFTIRQ-ON-W} state was registered at:
[ 10.192152][ C0] irq event stamp: 101196
[ 10.192693][ C0] hardirqs last enabled at (101196): _raw_spin_unlock_irqrestore (arch/x86/include/asm/irqflags.h:42 arch/x86/include/asm/irqflags.h:97 arch/x86/include/asm/irqflags.h:155 include/linux/spinlock_api_smp.h:151 kernel/locking/spinlock.c:194)
[ 10.193640][ C0] hardirqs last disabled at (101195): _raw_spin_lock_irqsave (arch/x86/include/asm/preempt.h:80 include/linux/spinlock_api_smp.h:109 kernel/locking/spinlock.c:162)
[ 10.194643][ C0] softirqs last enabled at (101168): handle_softirqs (kernel/softirq.c:408 kernel/softirq.c:589)
[ 10.195866][ C0] softirqs last disabled at (101173): run_ksoftirqd (kernel/softirq.c:418 kernel/softirq.c:951 kernel/softirq.c:942)
[ 10.197069][ C0]
[ 10.197069][ C0] other info that might help us debug this:
[ 10.198605][ C0] Possible unsafe locking scenario:
[ 10.198605][ C0]
[ 10.199624][ C0] CPU0
[ 10.200118][ C0] ----
[ 10.200607][ C0] lock(key_serial_lock);
[ 10.201190][ C0] <Interrupt>
[ 10.201699][ C0] lock(key_serial_lock);
[ 10.202284][ C0]
[ 10.202284][ C0] *** DEADLOCK ***
[ 10.202284][ C0]
[ 10.203553][ C0] 1 lock held by ksoftirqd/0/14:
[ 10.204145][ C0] #0: 431e5c64 (rcu_callback){....}-{0:0}, at: rcu_lock_acquire (include/linux/rcupdate.h:330)
[ 10.204992][ C0]
[ 10.204992][ C0] stack backtrace:
[ 10.205856][ C0] CPU: 0 UID: 0 PID: 14 Comm: ksoftirqd/0 Tainted: G T 6.14.0-05893-gaa52a1fbfc9a #1 PREEMPT(full)
[ 10.207648][ C0] Tainted: [T]=RANDSTRUCT
[ 10.208460][ C0] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
[ 10.209410][ C0] Call Trace:
[ 10.209878][ C0] ? dump_stack_lvl (lib/dump_stack.c:124)
[ 10.210436][ C0] ? dump_stack (lib/dump_stack.c:130)
[ 10.210988][ C0] ? print_usage_bug (kernel/locking/lockdep.c:4147 kernel/locking/lockdep.c:4295)
[ 10.211641][ C0] ? print_usage_bug (kernel/locking/lockdep.c:4011 (discriminator 1))
[ 10.212244][ C0] ? valid_state (kernel/locking/lockdep.c:4058)
[ 10.212822][ C0] ? mark_lock_irq (kernel/locking/lockdep.c:4268)
[ 10.213418][ C0] ? mark_lock (kernel/locking/lockdep.c:4754)
[ 10.213985][ C0] ? mark_usage (kernel/locking/lockdep.c:4643)
[ 10.214568][ C0] ? __lock_acquire (kernel/locking/lockdep.c:5189)
[ 10.215145][ C0] ? key_put (security/keys/key.c:663 security/keys/key.c:647)
[ 10.215661][ C0] ? lock_acquire (kernel/locking/lockdep.c:472 kernel/locking/lockdep.c:5868 kernel/locking/lockdep.c:5823)
[ 10.216212][ C0] ? key_put (security/keys/key.c:663 security/keys/key.c:647)
[ 10.216721][ C0] ? __lock_release+0x48/0x104
[ 10.217314][ C0] ? _raw_spin_lock (include/linux/spinlock_api_smp.h:134 kernel/locking/spinlock.c:154)
[ 10.217874][ C0] ? key_put (security/keys/key.c:663 security/keys/key.c:647)
[ 10.218407][ C0] ? key_put (security/keys/key.c:663 security/keys/key.c:647)
[ 10.218934][ C0] ? put_cred_rcu (kernel/cred.c:80)
[ 10.219497][ C0] ? rcu_do_batch (include/linux/rcupdate.h:341 kernel/rcu/tree.c:2570)
[ 10.220063][ C0] ? rcu_core (kernel/rcu/tree.c:2826)
[ 10.220629][ C0] ? rcu_core_si (kernel/rcu/tree.c:2842)
[ 10.221170][ C0] ? handle_softirqs (arch/x86/include/asm/atomic.h:23 include/linux/atomic/atomic-arch-fallback.h:457 include/linux/jump_label.h:262 include/trace/events/irq.h:142 kernel/softirq.c:562)
[ 10.221774][ C0] ? run_ksoftirqd (kernel/softirq.c:418 kernel/softirq.c:951 kernel/softirq.c:942)
[ 10.222312][ C0] ? smpboot_thread_fn (kernel/smpboot.c:164 (discriminator 3))
[ 10.222909][ C0] ? kthread (kernel/kthread.c:466)
[ 10.223434][ C0] ? sort_range (kernel/smpboot.c:107)
[ 10.223956][ C0] ? kthread_is_per_cpu (kernel/kthread.c:413)
[ 10.224522][ C0] ? ret_from_fork (arch/x86/kernel/process.c:159)
[ 10.225067][ C0] ? kthread_is_per_cpu (kernel/kthread.c:413)
[ 10.225638][ C0] ? ret_from_fork_asm (arch/x86/entry/entry_32.S:737)
[ 10.226210][ C0] ? entry_INT80_32 (arch/x86/entry/entry_32.S:942)
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20250331/202503312252.bef52733-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-03-31 14: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=202503312252.bef52733-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=jarkko@kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
/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.