syzbot


WARNING: locking bug in sched_core_lock

Status: auto-obsoleted due to no activity on 2024/11/19 11:57
Subsystems: kernel
[Documentation on labels]
Reported-by: syzbot+7279b9b6b0c7cb9c118b@syzkaller.appspotmail.com
First crash: 164d, last: 132d
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [kernel?] WARNING: locking bug in sched_core_lock 0 (1) 2024/07/14 04:24
Similar bugs (1)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream WARNING: locking bug in sched_core_lock (2) kernel 2 6d04h 24d 0/28 upstream: reported on 2024/11/27 06:53

Sample crash report:
------------[ cut here ]------------
DEBUG_LOCKS_WARN_ON(1)
WARNING: CPU: 0 PID: 7398 at kernel/locking/lockdep.c:231 hlock_class kernel/locking/lockdep.c:231 [inline]
WARNING: CPU: 0 PID: 7398 at kernel/locking/lockdep.c:231 check_wait_context kernel/locking/lockdep.c:4772 [inline]
WARNING: CPU: 0 PID: 7398 at kernel/locking/lockdep.c:231 __lock_acquire+0x58c/0x2040 kernel/locking/lockdep.c:5092
Modules linked in:
CPU: 0 UID: 0 PID: 7398 Comm: syz.3.598 Not tainted 6.11.0-rc2-syzkaller-00257-g5189dafa4cf9 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/27/2024
RIP: 0010:hlock_class kernel/locking/lockdep.c:231 [inline]
RIP: 0010:check_wait_context kernel/locking/lockdep.c:4772 [inline]
RIP: 0010:__lock_acquire+0x58c/0x2040 kernel/locking/lockdep.c:5092
Code: 00 00 83 3d 65 33 a8 0e 00 75 23 90 48 c7 c7 00 d4 0a 8c 48 c7 c6 a0 d6 0a 8c e8 ff d8 e5 ff 48 ba 00 00 00 00 00 fc ff df 90 <0f> 0b 90 90 90 31 db 48 81 c3 c4 00 00 00 48 89 d8 48 c1 e8 03 0f
RSP: 0018:ffffc90003c972d0 EFLAGS: 00010046
RAX: a8550caf17b10500 RBX: 0000000000001420 RCX: 0000000000040000
RDX: dffffc0000000000 RSI: 000000000003ffff RDI: 0000000000040000
RBP: 000000000000000f R08: ffffffff8155a2d2 R09: fffffbfff1cfa0d8
R10: dffffc0000000000 R11: fffffbfff1cfa0d8 R12: ffff8880215d1e00
R13: 0000000000001420 R14: 1ffff110042ba52f R15: ffff8880215d2978
FS:  00007ffb358336c0(0000) GS:ffff8880b9200000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000200e1000 CR3: 0000000067342000 CR4: 0000000000350ef0
Call Trace:
 <TASK>
 lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5759
 _raw_spin_lock_nested+0x31/0x40 kernel/locking/spinlock.c:378
 sched_core_lock+0x162/0x240 kernel/sched/core.c:341
 __sched_core_flip+0x176/0x440 kernel/sched/core.c:368
 __sched_core_enable kernel/sched/core.c:405 [inline]
 sched_core_get+0xbd/0x180 kernel/sched/core.c:423
 sched_core_alloc_cookie+0x71/0xa0 kernel/sched/core_sched.c:18
 sched_core_share_pid+0x298/0x7d0 kernel/sched/core_sched.c:185
 __do_sys_prctl kernel/sys.c:2729 [inline]
 __se_sys_prctl+0xe27/0x3990 kernel/sys.c:2457
 do_syscall_x64 arch/x86/entry/common.c:52 [inline]
 do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7ffb349779f9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffb35833038 EFLAGS: 00000246 ORIG_RAX: 000000000000009d
RAX: ffffffffffffffda RBX: 00007ffb34b05f80 RCX: 00007ffb349779f9
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 000000000000003e
RBP: 00007ffb349e58ee R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000002 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007ffb34b05f80 R15: 00007fff3aa8cb28
 </TASK>

Crashes (2):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/08/11 11:56 upstream 5189dafa4cf9 6f4edef4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root WARNING: locking bug in sched_core_lock
2024/07/10 04:22 upstream 34afb82a3c67 79d68ada .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root WARNING: locking bug in sched_core_lock
* Struck through repros no longer work on HEAD.