syzbot


BUG: scheduling while atomic in __bpf_arch_text_poke

Status: premoderation: reported on 2024/03/27 18:35
Reported-by: syzbot+18c2be2af37ab92088b6@syzkaller.appspotmail.com
First crash: 108d, last: 68d

Sample crash report:
BUG: scheduling while atomic: syz-executor.4/22509/0x00000002
Modules linked in:
Preemption disabled at:
[<ffffffff8187d638>] try_get_fmt_tmp_buf kernel/bpf/helpers.c:728 [inline]
[<ffffffff8187d638>] bpf_bprintf_prepare+0x118/0x1360 kernel/bpf/helpers.c:778
CPU: 1 PID: 22509 Comm: syz-executor.4 Not tainted 5.15.149-syzkaller-00490-g5d96939590c0 #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_slowpath+0xe/0x10 kernel/locking/mutex.c:1006
 mutex_lock+0x135/0x1e0 kernel/locking/mutex.c:288
 __bpf_arch_text_poke+0x369/0x5a0 arch/x86/net/bpf_jit_comp.c:363
 bpf_arch_text_poke+0x85/0xa0 arch/x86/net/bpf_jit_comp.c:387
 bpf_dispatcher_update kernel/bpf/dispatcher.c:125 [inline]
 bpf_dispatcher_change_prog+0xb07/0xcb0 kernel/bpf/dispatcher.c:156
 bpf_prog_change_xdp+0x24/0x30 net/core/filter.c:10782
 bpf_prog_test_run_xdp+0x821/0xbc0 net/bpf/test_run.c:826
 bpf_prog_test_run+0x3b0/0x630 kernel/bpf/syscall.c:3348
 __sys_bpf+0x525/0x760 kernel/bpf/syscall.c:4651
 __do_sys_bpf kernel/bpf/syscall.c:4737 [inline]
 __se_sys_bpf kernel/bpf/syscall.c:4735 [inline]
 __x64_sys_bpf+0x7c/0x90 kernel/bpf/syscall.c:4735
 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:0x7fd4625b2ca9
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:00007fd4613260c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000141
RAX: ffffffffffffffda RBX: 00007fd4626e0f80 RCX: 00007fd4625b2ca9
RDX: 000000000000000c RSI: 0000000020000500 RDI: 000000000000000a
RBP: 00007fd4625fe47e R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007fd4626e0f80 R15: 00007ffe86140b48
 </TASK>
: renamed from pim6reg1

Crashes (3):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/05/07 05:05 android13-5.15-lts 5d96939590c0 fa7a5cf0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-15-perf BUG: scheduling while atomic in __bpf_arch_text_poke
2024/05/06 22:34 android13-5.15-lts 5d96939590c0 fa7a5cf0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-15-perf BUG: scheduling while atomic in __bpf_arch_text_poke
2024/03/27 18:34 android13-5.15-lts 993bed180178 454571b6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-15-perf BUG: scheduling while atomic in __bpf_arch_text_poke
* Struck through repros no longer work on HEAD.