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-linux-6.13.y] [linux6.13.y] c358c65925: WARNING:possible_recursive_locking_detected
Date: Mon, 27 Jan 2025 23:00:01 +0800 [thread overview]
Message-ID: <202501272202.7e88153b-lkp@intel.com> (raw)
Hello,
kernel test robot noticed "WARNING:possible_recursive_locking_detected" on:
commit: c358c65925524fe1dfe962d59966a6aa01b5fc9b ("linux6.13.y-bore5.9.6")
https://github.com/steev/linux lenovo-x13s-linux-6.13.y
in testcase: boot
config: i386-randconfig-141-20250127
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)
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/202501272202.7e88153b-lkp@intel.com
[ 5.233830][ T1] WARNING: possible recursive locking detected
[ 5.234207][ T1] 6.13.0-00083-gc358c6592552 #2 Tainted: G T
[ 5.234652][ T1] --------------------------------------------
[ 5.235025][ T1] init/1 is trying to acquire lock:
[ 5.235318][ T1] b111ac44 (&p->se.child_burst.lock){+.+.}-{3:3}, at: update_child_burst_topological (kernel/sched/bore.c:168 kernel/sched/bore.c:226)
[ 5.235865][ T1]
[ 5.235865][ T1] but task is already holding lock:
[ 5.236248][ T1] b9a648c4 (&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)
[ 5.236742][ T1]
[ 5.236742][ T1] other info that might help us debug this:
[ 5.237166][ T1] Possible unsafe locking scenario:
[ 5.237166][ T1]
[ 5.237552][ T1] CPU0
[ 5.237725][ T1] ----
[ 5.237899][ T1] lock(&p->se.child_burst.lock);
[ 5.238166][ T1] lock(&p->se.child_burst.lock);
[ 5.238433][ T1]
[ 5.238433][ T1] *** DEADLOCK ***
[ 5.238433][ T1]
[ 5.238852][ T1] May be due to missing lock nesting notation
[ 5.238852][ T1]
[ 5.239281][ T1] 3 locks held by init/1:
[ 5.239506][ T1] #0: b9dd17f4 (cgroup_threadgroup_rwsem){.+.+}-{0:0}, at: cgroup_can_fork (kernel/cgroup/cgroup.c:6635)
[ 5.240001][ T1] #1: b9a31054 (tasklist_lock){.+.+}-{3:3}, at: sched_clone_bore (kernel/sched/bore.c:311)
[ 5.240463][ T1] #2: b9a648c4 (&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)
[ 5.240972][ T1]
[ 5.240972][ T1] stack backtrace:
[ 5.241279][ T1] CPU: 1 UID: 0 PID: 1 Comm: init Tainted: G T 6.13.0-00083-gc358c6592552 #2
[ 5.241805][ T1] Tainted: [T]=RANDSTRUCT
[ 5.242031][ T1] Call Trace:
[ 5.242206][ T1] dump_stack_lvl (lib/dump_stack.c:123)
[ 5.242445][ T1] dump_stack (lib/dump_stack.c:130)
[ 5.242658][ T1] print_deadlock_bug (kernel/locking/lockdep.c:3039)
[ 5.242923][ T1] validate_chain (kernel/locking/lockdep.c:3894)
[ 5.243170][ T1] __lock_acquire (kernel/locking/lockdep.c:5226)
[ 5.243417][ T1] lock_acquire (kernel/locking/lockdep.c:467 kernel/locking/lockdep.c:5851 kernel/locking/lockdep.c:5814)
[ 5.243651][ T1] ? update_child_burst_topological (kernel/sched/bore.c:168 kernel/sched/bore.c:226)
[ 5.243982][ T1] _raw_spin_lock (include/linux/spinlock_api_smp.h:134 kernel/locking/spinlock.c:154)
[ 5.244330][ T1] ? update_child_burst_topological (kernel/sched/bore.c:168 kernel/sched/bore.c:226)
[ 5.244824][ T1] update_child_burst_topological (kernel/sched/bore.c:168 kernel/sched/bore.c:226)
[ 5.245312][ T1] sched_clone_bore (kernel/sched/bore.c:267 kernel/sched/bore.c:312)
[ 5.245710][ T1] copy_process (kernel/fork.c:2522)
[ 5.246102][ T1] kernel_clone (include/linux/random.h:24 kernel/fork.c:2813)
[ 5.246460][ T1] ? lock_acquire (kernel/locking/lockdep.c:467 kernel/locking/lockdep.c:5851 kernel/locking/lockdep.c:5814)
[ 5.246844][ T1] ? find_held_lock (kernel/locking/lockdep.c:5339)
[ 5.247229][ T1] ? __lock_release+0x4e/0x150
[ 5.247660][ T1] __ia32_sys_clone (kernel/fork.c:2923)
[ 5.248058][ T1] ia32_sys_call (arch/x86/entry/syscall_32.c:44)
[ 5.248470][ T1] do_int80_syscall_32 (arch/x86/entry/common.c:165 arch/x86/entry/common.c:339)
[ 5.248894][ T1] entry_INT80_32 (arch/x86/entry/entry_32.S:945)
[ 5.249292][ T1] EIP: 0xa7e0a68a
[ 5.249602][ T1] Code: 33 04 00 83 c4 10 85 ed 0f 85 ea 00 00 00 31 d2 b8 78 00 00 00 65 8b 3d 08 00 00 00 bb 11 00 20 01 83 c7 68 89 d1 89 d6 cd 80 <89> c7 3d 00 f0 ff ff 0f 87 71 01 00 00 85 ff 0f 85 99 00 00 00 8b
All code
========
0: 33 04 00 xor (%rax,%rax,1),%eax
3: 83 c4 10 add $0x10,%esp
6: 85 ed test %ebp,%ebp
8: 0f 85 ea 00 00 00 jne 0xf8
e: 31 d2 xor %edx,%edx
10: b8 78 00 00 00 mov $0x78,%eax
15: 65 8b 3d 08 00 00 00 mov %gs:0x8(%rip),%edi # 0x24
1c: bb 11 00 20 01 mov $0x1200011,%ebx
21: 83 c7 68 add $0x68,%edi
24: 89 d1 mov %edx,%ecx
26: 89 d6 mov %edx,%esi
28: cd 80 int $0x80
2a:* 89 c7 mov %eax,%edi <-- trapping instruction
2c: 3d 00 f0 ff ff cmp $0xfffff000,%eax
31: 0f 87 71 01 00 00 ja 0x1a8
37: 85 ff test %edi,%edi
39: 0f 85 99 00 00 00 jne 0xd8
3f: 8b .byte 0x8b
Code starting with the faulting instruction
===========================================
0: 89 c7 mov %eax,%edi
2: 3d 00 f0 ff ff cmp $0xfffff000,%eax
7: 0f 87 71 01 00 00 ja 0x17e
d: 85 ff test %edi,%edi
f: 0f 85 99 00 00 00 jne 0xae
15: 8b .byte 0x8b
[ 5.251173][ T1] EAX: ffffffda EBX: 01200011 ECX: 00000000 EDX: 00000000
[ 5.251745][ T1] ESI: 00000000 EDI: a7d59da8 EBP: 00000000 ESP: afe31680
[ 5.252331][ T1] DS: 007b ES: 007b FS: 0000 GS: 0033 SS: 007b EFLAGS: 00000282
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20250127/202501272202.7e88153b-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-01-27 15:00 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=202501272202.7e88153b-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.