syzbot


BUG: scheduling while atomic in kernfs_activate

Status: premoderation: reported on 2024/04/07 02:26
Reported-by: syzbot+1501e0ca54c977db5a32@syzkaller.appspotmail.com
First crash: 68d, last: 68d

Sample crash report:
BUG: scheduling while atomic: syz-executor.1/9193/0x00000002
Modules linked in:
Preemption disabled at:
[<ffffffff8163d87f>] is_module_text_address+0x1f/0x360 kernel/module/main.c:3140
CPU: 0 PID: 9193 Comm: syz-executor.1 Not tainted 6.1.75-syzkaller-00123-g60534eef4739 #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
 rwsem_down_write_slowpath+0xddf/0x20a0 kernel/locking/rwsem.c:1227
 __down_write_common kernel/locking/rwsem.c:1357 [inline]
 __down_write kernel/locking/rwsem.c:1366 [inline]
 down_write+0x21/0x30 kernel/locking/rwsem.c:1619
 kernfs_activate+0x6a/0x200 fs/kernfs/dir.c:1353
 kernfs_add_one+0x2b4/0x3a0 fs/kernfs/dir.c:788
 __kernfs_create_file+0x1d8/0x270 fs/kernfs/file.c:1072
 sysfs_add_file_mode_ns+0x1c8/0x270 fs/sysfs/file.c:294
 sysfs_create_file_ns+0x193/0x2a0 fs/sysfs/file.c:355
 sysfs_create_file include/linux/sysfs.h:623 [inline]
 device_create_file drivers/base/core.c:3022 [inline]
 device_add+0x4d2/0xf10 drivers/base/core.c:3608
 netdev_register_kobject+0x177/0x320 net/core/net-sysfs.c:2011
 register_netdevice+0xe43/0x1490 net/core/dev.c:10103
 register_netdev+0x3c/0x50 net/core/dev.c:10229
 sit_init_net+0x244/0x500 net/ipv6/sit.c:1860
 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:0x7fac9127de69
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:00007fac920ba078 EFLAGS: 00000206 ORIG_RAX: 0000000000000038
RAX: ffffffffffffffda RBX: 00007fac913abf80 RCX: 00007fac9127de69
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 00000000660694c0
RBP: 00007fac912ca47a R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000206 R12: 0000000000000000
R13: 000000000000000b R14: 00007fac913abf80 R15: 00007ffe3c1ca438
 </TASK>

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/04/07 02:26 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 kernfs_activate
* Struck through repros no longer work on HEAD.