From: kernel test robot <oliver.sang@intel.com>
To: Steev Klimaszewski <steev@kali.org>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>, <oliver.sang@intel.com>
Subject: [steev:lenovo-x13s-6.16.0-rc5] [linux6.15.y] e9c2688b12: WARNING:possible_recursive_locking_detected
Date: Wed, 16 Jul 2025 14:10:07 +0800 [thread overview]
Message-ID: <202507160735.72c4502b-lkp@intel.com> (raw)
Hello,
kernel test robot noticed "WARNING:possible_recursive_locking_detected" on:
commit: e9c2688b128a46792eb108d001cd0e56b247cf27 ("linux6.15.y-bore5.9.6")
https://github.com/steev/linux lenovo-x13s-6.16.0-rc5
in testcase: trinity
version: trinity-i386-abe9de86-1_20230429
with following parameters:
runtime: 600s
config: x86_64-randconfig-r111-20250712
compiler: gcc-11
test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 16G
(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/202507160735.72c4502b-lkp@intel.com
[ 12.932716][ T1] WARNING: possible recursive locking detected
[ 12.933071][ T1] 6.16.0-rc5-00115-ge9c2688b128a #1 Not tainted
[ 12.933429][ T1] --------------------------------------------
[ 12.933782][ T1] systemd/1 is trying to acquire lock:
[ 12.934096][ T1] ffff9adac0328130 (&p->se.child_burst.lock){+.+.}-{3:3}, at: update_child_burst_topological (kernel/sched/bore.c:168 kernel/sched/bore.c:226)
[ 12.934756][ T1]
[ 12.934756][ T1] but task is already holding lock:
[ 12.935175][ T1] ffffffff9061f3f0 (&p->se.child_burst.lock){+.+.}-{3:3}, at: sched_clone_bore (kernel/sched/bore.c:168 kernel/sched/bore.c:266 kernel/sched/bore.c:312)
[ 12.935747][ T1]
[ 12.935747][ T1] other info that might help us debug this:
[ 12.936214][ T1] Possible unsafe locking scenario:
[ 12.936214][ T1]
[ 12.936638][ T1] CPU0
[ 12.936829][ T1] ----
[ 12.937020][ T1] lock(&p->se.child_burst.lock);
[ 12.937313][ T1] lock(&p->se.child_burst.lock);
[ 12.937607][ T1]
[ 12.937607][ T1] *** DEADLOCK ***
[ 12.937607][ T1]
[ 12.938066][ T1] May be due to missing lock nesting notation
[ 12.938066][ T1]
[ 12.950833][ T1] 3 locks held by systemd/1:
[ 12.951242][ T1] #0: ffffffff90ac9c20 (cgroup_threadgroup_rwsem){++++}-{0:0}, at: cgroup_can_fork (kernel/cgroup/cgroup.c:6671)
[ 12.952118][ T1] #1: ffffffff906080d8 (tasklist_lock){.+.+}-{3:3}, at: sched_clone_bore (kernel/sched/bore.c:311)
[ 12.952919][ T1] #2: ffffffff9061f3f0 (&p->se.child_burst.lock){+.+.}-{3:3}, at: sched_clone_bore (kernel/sched/bore.c:168 kernel/sched/bore.c:266 kernel/sched/bore.c:312)
[ 12.953794][ T1]
[ 12.953794][ T1] stack backtrace:
[ 12.954284][ T1] CPU: 1 UID: 0 PID: 1 Comm: systemd Not tainted 6.16.0-rc5-00115-ge9c2688b128a #1 PREEMPT(full)
[ 12.954289][ T1] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
[ 12.954291][ T1] Call Trace:
[ 12.954295][ T1] <TASK>
[ 12.954298][ T1] dump_stack_lvl (lib/dump_stack.c:123)
[ 12.955284][ T1] print_deadlock_bug (kernel/locking/lockdep.c:3047)
[ 12.955291][ T1] validate_chain (kernel/locking/lockdep.c:3901)
[ 12.955295][ T1] __lock_acquire (kernel/locking/lockdep.c:5240)
[ 12.955299][ T1] ? print_bad_irq_dependency (kernel/locking/lockdep.c:2600)
[ 12.955303][ T1] lock_acquire (kernel/locking/lockdep.c:473 kernel/locking/lockdep.c:5873)
[ 12.955306][ T1] ? update_child_burst_topological (kernel/sched/bore.c:168 kernel/sched/bore.c:226)
[ 12.955312][ T1] ? lock_acquire (kernel/locking/lockdep.c:473 kernel/locking/lockdep.c:5873)
[ 12.955316][ T1] _raw_spin_lock (include/linux/spinlock_api_smp.h:134 kernel/locking/spinlock.c:154)
[ 12.955320][ T1] ? update_child_burst_topological (kernel/sched/bore.c:168 kernel/sched/bore.c:226)
[ 12.955324][ T1] update_child_burst_topological (kernel/sched/bore.c:168 kernel/sched/bore.c:226)
[ 12.955329][ T1] sched_clone_bore (kernel/sched/bore.c:267 kernel/sched/bore.c:312)
[ 12.955334][ T1] copy_process (kernel/fork.c:2321)
[ 12.955341][ T1] kernel_clone (include/linux/random.h:26 kernel/fork.c:2606)
[ 12.955344][ T1] ? kvm_sched_clock_read (arch/x86/kernel/kvmclock.c:91)
[ 12.955347][ T1] ? local_clock_noinstr (kernel/sched/clock.c:301)
[ 12.955350][ T1] ? local_clock (arch/x86/include/asm/preempt.h:95 kernel/sched/clock.c:316)
[ 12.955352][ T1] ? __lock_release+0x12c/0x240
[ 12.955356][ T1] ? trace_preempt_on (include/trace/events/preemptirq.h:53 kernel/trace/trace_preemptirq.c:120)
[ 12.955363][ T1] __do_compat_sys_ia32_clone (arch/x86/kernel/sys_ia32.c:254)
[ 12.955371][ T1] do_int80_emulation (arch/x86/entry/syscall_32.c:83 arch/x86/entry/syscall_32.c:172)
[ 12.955379][ T1] ? trace_irq_disable+0x25/0xc0
[ 12.955382][ T1] ? do_int80_emulation (include/linux/entry-common.h:119 arch/x86/entry/syscall_32.c:145)
[ 12.955386][ T1] asm_int80_emulation (arch/x86/include/asm/idtentry.h:626)
[ 12.955390][ T1] RIP: 0023:0xf7f1e092
[ 12.955395][ T1] Code: 00 00 00 e9 90 ff ff ff ff a3 24 00 00 00 68 30 00 00 00 e9 80 ff ff ff ff a3 f8 ff ff ff 66 90 00 00 00 00 00 00 00 00 cd 80 <c3> 8d b4 26 00 00 00 00 8d b6 00 00 00 00 8b 1c 24 c3 8d b4 26 00
All code
========
0: 00 00 add %al,(%rax)
2: 00 e9 add %ch,%cl
4: 90 nop
5: ff (bad)
6: ff (bad)
7: ff (bad)
8: ff a3 24 00 00 00 jmp *0x24(%rbx)
e: 68 30 00 00 00 push $0x30
13: e9 80 ff ff ff jmp 0xffffffffffffff98
18: ff a3 f8 ff ff ff jmp *-0x8(%rbx)
1e: 66 90 xchg %ax,%ax
...
28: cd 80 int $0x80
2a:* c3 ret <-- trapping instruction
2b: 8d b4 26 00 00 00 00 lea 0x0(%rsi,%riz,1),%esi
32: 8d b6 00 00 00 00 lea 0x0(%rsi),%esi
38: 8b 1c 24 mov (%rsp),%ebx
3b: c3 ret
3c: 8d .byte 0x8d
3d: b4 26 mov $0x26,%ah
...
Code starting with the faulting instruction
===========================================
0: c3 ret
1: 8d b4 26 00 00 00 00 lea 0x0(%rsi,%riz,1),%esi
8: 8d b6 00 00 00 00 lea 0x0(%rsi),%esi
e: 8b 1c 24 mov (%rsp),%ebx
11: c3 ret
12: 8d .byte 0x8d
13: b4 26 mov $0x26,%ah
...
[ 12.955398][ T1] RSP: 002b:00000000ffddbf1c EFLAGS: 00200282 ORIG_RAX: 0000000000000078
[ 12.955401][ T1] RAX: ffffffffffffffda RBX: 0000000001200011 RCX: 0000000000000000
[ 12.955403][ T1] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 00000000f72808a8
[ 12.955405][ T1] RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
[ 12.955406][ T1] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
[ 12.955407][ T1] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
[ 12.955412][ T1] </TASK>
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20250716/202507160735.72c4502b-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-07-16 6:10 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=202507160735.72c4502b-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=steev@kali.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.