syzbot


WARNING: locking bug in rto_push_irq_work_func

Status: upstream: reported on 2024/10/14 23:55
Subsystems: net
[Documentation on labels]
Reported-by: syzbot+da051a9137a15fa8ecdf@syzkaller.appspotmail.com
First crash: 41d, last: 12d
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [kernel?] WARNING: locking bug in rto_push_irq_work_func 0 (1) 2024/10/14 23:55

Sample crash report:
=============================
[ BUG: Invalid wait context ]
6.12.0-rc6-syzkaller-00169-g906bd684e4b1 #0 Not tainted
-----------------------------
syz.1.631/8819 is trying to lock:
ffff8880b863ea98 (subsys mutex#59){+.+.}-{3:3}, at: raw_spin_rq_lock_nested+0xb0/0x140 kernel/sched/core.c:606
other info that might help us debug this:
context-{2:2}
1 lock held by syz.1.631/8819:
 #0: ffff888024e82f10 (&u->iolock){+.+.}-{3:3}, at: __unix_dgram_recvmsg+0x246/0x12f0 net/unix/af_unix.c:2432
stack backtrace:
CPU: 0 UID: 0 PID: 8819 Comm: syz.1.631 Not tainted 6.12.0-rc6-syzkaller-00169-g906bd684e4b1 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/30/2024
Call Trace:
 <IRQ>
 __dump_stack lib/dump_stack.c:94 [inline]
 dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120
 print_lock_invalid_wait_context kernel/locking/lockdep.c:4802 [inline]
 check_wait_context kernel/locking/lockdep.c:4874 [inline]
 __lock_acquire+0x154a/0x2050 kernel/locking/lockdep.c:5152
 lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5825
 _raw_spin_lock_nested+0x31/0x40 kernel/locking/spinlock.c:378
 raw_spin_rq_lock_nested+0xb0/0x140 kernel/sched/core.c:606
 raw_spin_rq_lock kernel/sched/sched.h:1505 [inline]
 rto_push_irq_work_func+0x86/0x350 kernel/sched/rt.c:2259
 irq_work_single+0x136/0x240 kernel/irq_work.c:221
 __flush_smp_call_function_queue+0xa17/0x1690 kernel/smp.c:574
 __sysvec_call_function_single+0xb8/0x430 arch/x86/kernel/smp.c:271
 instr_sysvec_call_function_single arch/x86/kernel/smp.c:266 [inline]
 sysvec_call_function_single+0x9e/0xc0 arch/x86/kernel/smp.c:266
 </IRQ>
 <TASK>
 asm_sysvec_call_function_single+0x1a/0x20 arch/x86/include/asm/idtentry.h:709
RIP: 0010:__raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:152 [inline]
RIP: 0010:_raw_spin_unlock_irqrestore+0xd8/0x140 kernel/locking/spinlock.c:194
Code: 9c 8f 44 24 20 42 80 3c 23 00 74 08 4c 89 f7 e8 be 9a 2d f6 f6 44 24 21 02 75 52 41 f7 c7 00 02 00 00 74 01 fb bf 01 00 00 00 <e8> 93 2a 92 f5 65 8b 05 04 d2 32 74 85 c0 74 43 48 c7 04 24 0e 36
RSP: 0018:ffffc9000c097540 EFLAGS: 00000206
RAX: 837d1219b39e9400 RBX: 1ffff92001812eac RCX: ffffffff8170bffa
RDX: dffffc0000000000 RSI: ffffffff8c0acac0 RDI: 0000000000000001
RBP: ffffc9000c0975d0 R08: ffffffff942cd8af R09: 1ffffffff2859b15
R10: dffffc0000000000 R11: fffffbfff2859b16 R12: dffffc0000000000
R13: 1ffff92001812ea8 R14: ffffc9000c097560 R15: 0000000000000246
 spin_unlock_irqrestore include/linux/spinlock.h:406 [inline]
 __skb_try_recv_datagram+0x1cb/0x6a0 net/core/datagram.c:266
 __unix_dgram_recvmsg+0x3ba/0x12f0 net/unix/af_unix.c:2435
 sock_recvmsg_nosec+0x190/0x1d0 net/socket.c:1051
 ____sys_recvmsg+0x3cd/0x480 net/socket.c:2824
 ___sys_recvmsg net/socket.c:2868 [inline]
 do_recvmmsg+0x45e/0xad0 net/socket.c:2962
 __sys_recvmmsg net/socket.c:3041 [inline]
 __do_sys_recvmmsg net/socket.c:3064 [inline]
 __se_sys_recvmmsg net/socket.c:3057 [inline]
 __x64_sys_recvmmsg+0x199/0x250 net/socket.c:3057
 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:0x7feef777e719
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:00007feef84ff038 EFLAGS: 00000246 ORIG_RAX: 000000000000012b
RAX: ffffffffffffffda RBX: 00007feef7936058 RCX: 00007feef777e719
RDX: 0000000000010106 RSI: 00000000200000c0 RDI: 0000000000000004
RBP: 00007feef77f139e R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000002 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007feef7936058 R15: 00007ffc942f53f8
 </TASK>
----------------
Code disassembly (best guess):
   0:	9c                   	pushf
   1:	8f 44 24 20          	pop    0x20(%rsp)
   5:	42 80 3c 23 00       	cmpb   $0x0,(%rbx,%r12,1)
   a:	74 08                	je     0x14
   c:	4c 89 f7             	mov    %r14,%rdi
   f:	e8 be 9a 2d f6       	call   0xf62d9ad2
  14:	f6 44 24 21 02       	testb  $0x2,0x21(%rsp)
  19:	75 52                	jne    0x6d
  1b:	41 f7 c7 00 02 00 00 	test   $0x200,%r15d
  22:	74 01                	je     0x25
  24:	fb                   	sti
  25:	bf 01 00 00 00       	mov    $0x1,%edi
* 2a:	e8 93 2a 92 f5       	call   0xf5922ac2 <-- trapping instruction
  2f:	65 8b 05 04 d2 32 74 	mov    %gs:0x7432d204(%rip),%eax        # 0x7432d23a
  36:	85 c0                	test   %eax,%eax
  38:	74 43                	je     0x7d
  3a:	48                   	rex.W
  3b:	c7                   	.byte 0xc7
  3c:	04 24                	add    $0x24,%al
  3e:	0e                   	(bad)
  3f:	36                   	ss

Crashes (2):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/11/08 09:29 upstream 906bd684e4b1 179b040e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root WARNING: locking bug in rto_push_irq_work_func
2024/10/10 23:44 upstream eb952c47d154 8fbfc0c8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root WARNING: locking bug in rto_push_irq_work_func
* Struck through repros no longer work on HEAD.