syzbot


BUG: sleeping function called from invalid context in bpf_check

Status: upstream: reported C repro on 2024/02/17 20:30
Bug presence: origin:lts-only
[Documentation on labels]
Reported-by: syzbot+7f40595d3b498be6533f@syzkaller.appspotmail.com
First crash: 75d, last: 75d
Bug presence (2)
Date Name Commit Repro Result
2024/02/17 linux-5.15.y (ToT) 6139f2a02fe0 C [report] BUG: scheduling while atomic in exit_to_user_mode_loop
2024/02/17 upstream (ToT) f2667e0c3240 C Didn't crash
Fix bisection attempts (1)
Created Duration User Patch Repo Result
2024/02/23 18:15 5h39m fix candidate upstream job log (1)

Sample crash report:
BUG: sleeping function called from invalid context at include/linux/sched/mm.h:209
in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 6544, name: syz-executor370
no locks held by syz-executor370/6544.
Preemption disabled at:
[<0000000000000000>] 0x0
CPU: 0 PID: 6544 Comm: syz-executor370 Not tainted 5.15.148-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
 ___might_sleep+0x547/0x6a0 kernel/sched/core.c:9626
 might_alloc include/linux/sched/mm.h:209 [inline]
 slab_pre_alloc_hook+0x44/0xc0 mm/slab.h:492
 slab_alloc_node mm/slub.c:3134 [inline]
 __kmalloc_node+0x71/0x390 mm/slub.c:4451
 kmalloc_node include/linux/slab.h:614 [inline]
 __vmalloc_area_node mm/vmalloc.c:2910 [inline]
 __vmalloc_node_range+0x2e2/0x8c0 mm/vmalloc.c:3029
 __vmalloc_node mm/vmalloc.c:3079 [inline]
 vzalloc+0x75/0x80 mm/vmalloc.c:3149
 bpf_check+0x1e8/0x12d00 kernel/bpf/verifier.c:13973
 bpf_prog_load+0x12b3/0x1b60 kernel/bpf/syscall.c:2325
 __sys_bpf+0x343/0x670 kernel/bpf/syscall.c:4623
 __do_sys_bpf kernel/bpf/syscall.c:4727 [inline]
 __se_sys_bpf kernel/bpf/syscall.c:4725 [inline]
 __x64_sys_bpf+0x78/0x90 kernel/bpf/syscall.c:4725
 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:0x7f1789b57ee9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 c1 17 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffdfec01888 EFLAGS: 00000246 ORIG_RAX: 0000000000000141
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f1789b57ee9
RDX: 0000000000000049 RSI: 0000000020000980 RDI: 0000000000000005
RBP: 00000000000f4240 R08: 0000000000000000 R09: 00000000000000a0
R10: 0000000000000000 R11: 0000000000000246 R12: 00000000000175b9
R13: 00007ffdfec0189c R14: 00007ffdfec018b0 R15: 00007ffdfec018a0
 </TASK>
BUG: scheduling while atomic: syz-executor370/6544/0x00000002
no locks held by syz-executor370/6544.
Modules linked in:
Preemption disabled at:
[<0000000000000000>] 0x0

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/02/17 20:30 linux-5.15.y 6139f2a02fe0 578f7538 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf BUG: sleeping function called from invalid context in bpf_check
* Struck through repros no longer work on HEAD.