syzbot


WARNING: locking bug in sched_tick

Status: upstream: reported on 2024/07/11 21:22
Subsystems: kernel
[Documentation on labels]
Reported-by: syzbot+6212b93592985c1211e8@syzkaller.appspotmail.com
First crash: 62d, last: 11d
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [kernel?] WARNING: locking bug in sched_tick 0 (1) 2024/07/11 21:22

Sample crash report:
------------[ cut here ]------------
DEBUG_LOCKS_WARN_ON(1)
WARNING: CPU: 1 PID: 0 at kernel/locking/lockdep.c:231 hlock_class kernel/locking/lockdep.c:231 [inline]
WARNING: CPU: 1 PID: 0 at kernel/locking/lockdep.c:231 check_wait_context kernel/locking/lockdep.c:4772 [inline]
WARNING: CPU: 1 PID: 0 at kernel/locking/lockdep.c:231 __lock_acquire+0x58c/0x2040 kernel/locking/lockdep.c:5092
Modules linked in:
CPU: 1 UID: 0 PID: 0 Comm: swapper/1 Not tainted 6.11.0-rc5-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/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 a5 4e a8 0e 00 75 23 90 48 c7 c7 e0 d3 0a 8c 48 c7 c6 80 d6 0a 8c e8 7f 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:ffffc90000a189d0 EFLAGS: 00010046
RAX: 18003eb46ed68a00 RBX: 0000000000000f98 RCX: ffff8880182f0000
RDX: dffffc0000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000005 R08: ffffffff8155b4d2 R09: fffffbfff1cfa0e0
R10: dffffc0000000000 R11: fffffbfff1cfa0e0 R12: ffff8880182f0000
R13: 0000000000000f98 R14: 1ffff1100305e165 R15: ffff8880182f0b28
FS:  0000000000000000(0000) GS:ffff8880b9300000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b30f1eff8 CR3: 000000005ea04000 CR4: 0000000000350ef0
Call Trace:
 <IRQ>
 lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5759
 _raw_spin_lock_nested+0x31/0x40 kernel/locking/spinlock.c:378
 raw_spin_rq_lock_nested+0xb0/0x140 kernel/sched/core.c:568
 raw_spin_rq_lock kernel/sched/sched.h:1415 [inline]
 rq_lock kernel/sched/sched.h:1714 [inline]
 sched_tick+0x72/0x610 kernel/sched/core.c:5458
 update_process_times+0x202/0x230 kernel/time/timer.c:2490
 tick_sched_handle kernel/time/tick-sched.c:276 [inline]
 tick_nohz_handler+0x37c/0x500 kernel/time/tick-sched.c:297
 __run_hrtimer kernel/time/hrtimer.c:1689 [inline]
 __hrtimer_run_queues+0x553/0xd50 kernel/time/hrtimer.c:1753
 hrtimer_interrupt+0x396/0x990 kernel/time/hrtimer.c:1815
 local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1032 [inline]
 __sysvec_apic_timer_interrupt+0x112/0x3f0 arch/x86/kernel/apic/apic.c:1049
 instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1043 [inline]
 sysvec_apic_timer_interrupt+0xa1/0xc0 arch/x86/kernel/apic/apic.c:1043
 </IRQ>
 <TASK>
 asm_sysvec_apic_timer_interrupt+0x1a/0x20 arch/x86/include/asm/idtentry.h:702
RIP: 0010:sched_core_balance+0x152/0x1180 kernel/sched/core.c:6198
Code: 00 48 c7 c2 e0 87 0a 8c e8 8b fa 0a 00 4c 89 7c 24 68 e9 a9 0f 00 00 4c 89 ff e8 e9 bf 5b 0a e8 64 bd 35 00 fb 4c 8b 6c 24 18 <41> 83 fd 08 0f 83 78 0f 00 00 4e 8d 3c e5 40 7a 29 8e 4c 89 f8 48
RSP: 0018:ffffc900001a79a0 EFLAGS: 00000286
RAX: 18003eb46ed68a00 RBX: ffff8880b933f748 RCX: ffffffff94f2c903
RDX: dffffc0000000000 RSI: ffffffff8c0ad540 RDI: ffffffff8c606ec0
RBP: ffffc900001a7b20 R08: ffffffff9017f7ef R09: 1ffffffff202fefd
R10: dffffc0000000000 R11: fffffbfff202fefe R12: 0000000000000001
R13: 0000000000000001 R14: dffffc0000000000 R15: ffff8880b933e9c0
 do_balance_callbacks kernel/sched/core.c:4840 [inline]
 __balance_callbacks+0x18a/0x280 kernel/sched/core.c:4894
 finish_lock_switch kernel/sched/core.c:4941 [inline]
 finish_task_switch+0x1d3/0x870 kernel/sched/core.c:5060
 context_switch kernel/sched/core.c:5191 [inline]
 __schedule+0x1808/0x4a60 kernel/sched/core.c:6529
 schedule_idle+0x53/0x90 kernel/sched/core.c:6647
 do_idle+0x56a/0x5d0 kernel/sched/idle.c:354
 cpu_startup_entry+0x42/0x60 kernel/sched/idle.c:424
 start_secondary+0x100/0x100 arch/x86/kernel/smpboot.c:313
 common_startup_64+0x13e/0x147
 </TASK>
----------------
Code disassembly (best guess):
   0:	00 48 c7             	add    %cl,-0x39(%rax)
   3:	c2 e0 87             	ret    $0x87e0
   6:	0a 8c e8 8b fa 0a 00 	or     0xafa8b(%rax,%rbp,8),%cl
   d:	4c 89 7c 24 68       	mov    %r15,0x68(%rsp)
  12:	e9 a9 0f 00 00       	jmp    0xfc0
  17:	4c 89 ff             	mov    %r15,%rdi
  1a:	e8 e9 bf 5b 0a       	call   0xa5bc008
  1f:	e8 64 bd 35 00       	call   0x35bd88
  24:	fb                   	sti
  25:	4c 8b 6c 24 18       	mov    0x18(%rsp),%r13
* 2a:	41 83 fd 08          	cmp    $0x8,%r13d <-- trapping instruction
  2e:	0f 83 78 0f 00 00    	jae    0xfac
  34:	4e 8d 3c e5 40 7a 29 	lea    -0x71d685c0(,%r12,8),%r15
  3b:	8e
  3c:	4c 89 f8             	mov    %r15,%rax
  3f:	48                   	rex.W

Crashes (3):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/08/27 05:23 upstream 5be63fc19fca 9aee4e0b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root WARNING: locking bug in sched_tick
2024/08/03 01:28 upstream 948752d2e010 53683cf2 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root WARNING: locking bug in sched_tick
2024/07/07 21:10 upstream c6653f49e4fd bc4ebbb5 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root WARNING: locking bug in sched_tick
* Struck through repros no longer work on HEAD.