syzbot


BUG: scheduling while atomic in sock_alloc_send_pskb

Status: auto-obsoleted due to no activity on 2024/07/04 10:43
Reported-by: syzbot+965d293ad1af05ef104f@syzkaller.appspotmail.com
First crash: 103d, last: 103d

Sample crash report:
BUG: scheduling while atomic: syz-executor.1/26384/0x00000002
Modules linked in:
Preemption disabled at:
[<ffffffff81aca9b7>] kmap_atomic include/linux/highmem-internal.h:196 [inline]
[<ffffffff81aca9b7>] clear_highpage include/linux/highmem.h:180 [inline]
[<ffffffff81aca9b7>] kernel_init_free_pages+0x47/0xf0 mm/page_alloc.c:1407
CPU: 1 PID: 26384 Comm: syz-executor.1 Tainted: G        W         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_timeout+0xa9/0x370 kernel/time/timer.c:1866
 sock_wait_for_wmem net/core/sock.c:2484 [inline]
 sock_alloc_send_pskb+0x70e/0xa50 net/core/sock.c:2523
 unix_stream_sendpage+0x77c/0x11a0 net/unix/af_unix.c:2162
 kernel_sendpage+0x251/0x2d0 net/socket.c:3534
 sock_sendpage+0x85/0xb0 net/socket.c:1025
 pipe_to_sendpage+0x257/0x340 fs/splice.c:364
 splice_from_pipe_feed fs/splice.c:418 [inline]
 __splice_from_pipe+0x339/0x860 fs/splice.c:562
 splice_from_pipe fs/splice.c:597 [inline]
 generic_splice_sendpage+0x195/0x220 fs/splice.c:746
 do_splice_from fs/splice.c:767 [inline]
 direct_splice_actor+0xff/0x130 fs/splice.c:936
 splice_direct_to_actor+0x4f1/0xbe0 fs/splice.c:891
 do_splice_direct+0x27f/0x3c0 fs/splice.c:979
 do_sendfile+0x616/0xfe0 fs/read_write.c:1249
 __do_sys_sendfile64 fs/read_write.c:1317 [inline]
 __se_sys_sendfile64 fs/read_write.c:1303 [inline]
 __x64_sys_sendfile64+0x1ce/0x230 fs/read_write.c:1303
 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:0x7f2505125e69
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:00007f2503e780c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000028
RAX: ffffffffffffffda RBX: 00007f2505254050 RCX: 00007f2505125e69
RDX: 0000000000000000 RSI: 000000000000000e RDI: 000000000000000d
RBP: 00007f250517247a R08: 0000000000000000 R09: 0000000000000000
R10: 000080001d00c0cd R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007f2505254050 R15: 00007ffd0e250b08
 </TASK>

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