syzbot


BUG: scheduling while atomic in rtnl_lock_killable

Status: premoderation: reported on 2024/04/08 04:16
Reported-by: syzbot+df07901ffec76a22a605@syzkaller.appspotmail.com
First crash: 71d, last: 56d
Similar bugs (1)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
android-5-15 BUG: scheduling while atomic in rtnl_lock_killable 1 68d 68d 0/2 premoderation: reported on 2024/04/11 01:33

Sample crash report:
BUG: scheduling while atomic: syz-executor.1/12800/0x00000002
Modules linked in:
Preemption disabled at:
[<ffffffff84ef3bb1>] ida_alloc_range+0x251/0xa60 lib/idr.c:395
CPU: 0 PID: 12800 Comm: syz-executor.1 Not tainted 6.1.75-syzkaller-00064-g3dfddcb9c277 #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/0x1b lib/dump_stack.c:113
 __schedule_bug+0x195/0x260 kernel/sched/core.c:5960
 schedule_debug kernel/sched/core.c:5987 [inline]
 __schedule+0xcf7/0x1550 kernel/sched/core.c:6622
 schedule+0xc3/0x180 kernel/sched/core.c:6805
 schedule_preempt_disabled+0x13/0x20 kernel/sched/core.c:6864
 mutex_optimistic_spin kernel/locking/mutex.c:529 [inline]
 __mutex_lock_common kernel/locking/mutex.c:629 [inline]
 __mutex_lock+0x5b6/0x1ca0 kernel/locking/mutex.c:774
 __mutex_lock_killable_slowpath+0xe/0x10 kernel/locking/mutex.c:1069
 mutex_lock_killable+0x132/0x1e0 kernel/locking/mutex.c:1036
 rtnl_lock_killable+0x15/0x20 net/core/rtnetlink.c:80
 register_netdev+0x14/0x50 net/core/dev.c:10227
 loopback_net_init+0x74/0x150 drivers/net/loopback.c:219
 ops_init+0x1cf/0x490 net/core/net_namespace.c:135
 setup_net+0x4ca/0xd60 net/core/net_namespace.c:332
 copy_net_ns+0x35c/0x5b0 net/core/net_namespace.c:478
 create_new_namespaces+0x416/0x670 kernel/nsproxy.c:110
 copy_namespaces+0x1d1/0x220 kernel/nsproxy.c:178
 copy_process+0x12e2/0x3530 kernel/fork.c:2373
 kernel_clone+0x229/0x890 kernel/fork.c:2786
 __do_sys_clone kernel/fork.c:2929 [inline]
 __se_sys_clone kernel/fork.c:2913 [inline]
 __x64_sys_clone+0x231/0x280 kernel/fork.c:2913
 do_syscall_x64 arch/x86/entry/common.c:51 [inline]
 do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:81
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f6b6747dea9
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:00007f6b68168078 EFLAGS: 00000206 ORIG_RAX: 0000000000000038
RAX: ffffffffffffffda RBX: 00007f6b675abf80 RCX: 00007f6b6747dea9
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 00000000660694c0
RBP: 00007f6b674ca4a4 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000206 R12: 0000000000000000
R13: 000000000000000b R14: 00007f6b675abf80 R15: 00007ffd6a04d0c8
 </TASK>

Crashes (3):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/04/23 07:59 android14-6.1 3dfddcb9c277 21339d7b .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-6-1-perf BUG: scheduling while atomic in rtnl_lock_killable
2024/04/22 16:38 android14-6.1 dcb09569bbff 36c961ad .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-6-1-perf BUG: scheduling while atomic in rtnl_lock_killable
2024/04/08 04:15 android14-6.1 60534eef4739 ca620dd8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-6-1-perf BUG: scheduling while atomic in rtnl_lock_killable
* Struck through repros no longer work on HEAD.