syzbot


BUG: scheduling while atomic in pcpu_alloc

Status: auto-obsoleted due to no activity on 2024/07/05 18:06
Reported-by: syzbot+fecb38d285907d5ea3dc@syzkaller.appspotmail.com
First crash: 106d, last: 99d
Similar bugs (1)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
android-6-1 BUG: scheduling while atomic in pcpu_alloc 11 62d 122d 0/2 premoderation: reported on 2024/03/14 04:57

Sample crash report:
BUG: scheduling while atomic: syz-executor.3/28134/0x00000002
Modules linked in:
Preemption disabled at:
[<ffffffff8165ea9a>] is_module_text_address+0x1a/0x140 kernel/module.c:4811
CPU: 0 PID: 28134 Comm: syz-executor.3 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_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_killable_slowpath+0xe/0x10 kernel/locking/mutex.c:1012
 mutex_lock_killable+0x137/0x1e0 kernel/locking/mutex.c:979
 pcpu_alloc+0x2a8/0x13e0 mm/percpu.c:1774
 __alloc_percpu_gfp+0x27/0x30 mm/percpu.c:1937
 bpf_map_alloc_percpu+0xe6/0x160 kernel/bpf/syscall.c:457
 bpf_array_alloc_percpu kernel/bpf/arraymap.c:37 [inline]
 array_map_alloc+0x3a5/0x6d0 kernel/bpf/arraymap.c:150
 find_and_alloc_map kernel/bpf/syscall.c:129 [inline]
 map_create+0x411/0x2050 kernel/bpf/syscall.c:857
 __sys_bpf+0x296/0x760 kernel/bpf/syscall.c:4609
 __do_sys_bpf kernel/bpf/syscall.c:4731 [inline]
 __se_sys_bpf kernel/bpf/syscall.c:4729 [inline]
 __x64_sys_bpf+0x7c/0x90 kernel/bpf/syscall.c:4729
 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:0x7f407f8b0e69
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:00007f407e6240c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000141
RAX: ffffffffffffffda RBX: 00007f407f9def80 RCX: 00007f407f8b0e69
RDX: 0000000000000048 RSI: 0000000020000140 RDI: 2000000000000000
RBP: 00007f407f8fd47a R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007f407f9def80 R15: 00007ffd2e9373b8
 </TASK>

Crashes (4):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/04/06 17:57 android13-5.15-lts 993bed180178 ca620dd8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-15 BUG: scheduling while atomic in pcpu_alloc
2024/04/03 11:28 android13-5.15-lts 993bed180178 7925100d .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-15-perf BUG: scheduling while atomic in pcpu_alloc
2024/04/03 04:54 android13-5.15-lts 993bed180178 7925100d .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-15-perf BUG: scheduling while atomic in pcpu_alloc
2024/03/30 01:59 android13-5.15-lts 993bed180178 6baf5069 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-15-perf BUG: scheduling while atomic in pcpu_alloc
* Struck through repros no longer work on HEAD.