syzbot


BUG: scheduling while atomic in rtnl_lock_killable

Status: auto-obsoleted due to no activity on 2024/07/10 01:37
Reported-by: syzbot+a7f254c5c233ef00cdfa@syzkaller.appspotmail.com
First crash: 97d, last: 97d
Similar bugs (1)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
android-6-1 BUG: scheduling while atomic in rtnl_lock_killable 3 85d 100d 0/2 premoderation: reported on 2024/04/08 04:16

Sample crash report:
BUG: scheduling while atomic: syz-executor.2/6749/0x00000002
Modules linked in:
Preemption disabled at:
[<ffffffff8285ca83>] ida_alloc_range+0x253/0xa80 lib/idr.c:395
CPU: 0 PID: 6749 Comm: syz-executor.2 Not tainted 5.15.148-syzkaller-00718-g993bed180178 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x151/0x1b7 lib/dump_stack.c:106
 dump_stack+0x15/0x17 lib/dump_stack.c:113
 __schedule_bug+0x195/0x260 kernel/sched/core.c:5707
 schedule_debug kernel/sched/core.c:5734 [inline]
 __schedule+0xd19/0x1590 kernel/sched/core.c:6402
 schedule+0x11f/0x1e0 kernel/sched/core.c:6595
 schedule_preempt_disabled+0x13/0x20 kernel/sched/core.c:6654
 mutex_optimistic_spin kernel/locking/mutex.c:521 [inline]
 __mutex_lock_common kernel/locking/mutex.c:620 [inline]
 __mutex_lock+0x5b5/0x1870 kernel/locking/mutex.c:755
 __mutex_lock_killable_slowpath+0xe/0x10 kernel/locking/mutex.c:1012
 mutex_lock_killable+0x137/0x1e0 kernel/locking/mutex.c:979
 rtnl_lock_killable+0x15/0x20 net/core/rtnetlink.c:78
 register_netdev+0x14/0x50 net/core/dev.c:10483
 loopback_net_init+0x74/0x150 drivers/net/loopback.c:216
 ops_init+0x1cf/0x4a0 net/core/net_namespace.c:135
 setup_net+0x34b/0xb50 net/core/net_namespace.c:329
 copy_net_ns+0x35c/0x5b0 net/core/net_namespace.c:473
 create_new_namespaces+0x416/0x670 kernel/nsproxy.c:110
 copy_namespaces+0x1d1/0x220 kernel/nsproxy.c:178
 copy_process+0x1174/0x3290 kernel/fork.c:2267
 kernel_clone+0x21e/0x9e0 kernel/fork.c:2662
 __do_sys_clone kernel/fork.c:2788 [inline]
 __se_sys_clone kernel/fork.c:2772 [inline]
 __x64_sys_clone+0x23f/0x290 kernel/fork.c:2772
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f37b40cce69
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 00 00 90 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 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f37b2e40078 EFLAGS: 00000206 ORIG_RAX: 0000000000000038
RAX: ffffffffffffffda RBX: 00007f37b41faf80 RCX: 00007f37b40cce69
RDX: 0000000000000000 RSI: 0000000001000000 RDI: 00000000c0920400
RBP: 00007f37b411947a R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000206 R12: 0000000000000000
R13: 000000000000000b R14: 00007f37b41faf80 R15: 00007ffff6f4c128
 </TASK>

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/04/11 01:32 android13-5.15-lts 993bed180178 33b9e058 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-15-perf BUG: scheduling while atomic in rtnl_lock_killable
* Struck through repros no longer work on HEAD.