syzbot


BUG: scheduling while atomic in trace_set_clr_event

Status: upstream: reported C repro on 2024/02/14 06:37
Bug presence: origin:lts
[Documentation on labels]
Reported-by: syzbot+f86125c57114fccdaa69@syzkaller.appspotmail.com
First crash: 74d, last: 19d
Bug presence (2)
Date Name Commit Repro Result
2024/02/14 lts (merge base) 6139f2a02fe0 C [report] BUG: scheduling while atomic in exit_to_user_mode_loop
2024/02/14 upstream (ToT) 7e90b5c295ec C Didn't crash
Last patch testing requests (6)
Created Duration User Patch Repo Result
2024/03/22 08:39 5m retest repro android13-5.15-lts report log
2024/03/05 03:17 10m retest repro android13-5.15-lts report log
2024/03/05 02:58 13m retest repro android13-5.15-lts report log
2024/03/05 02:58 13m retest repro android13-5.15-lts report log
2024/03/05 02:05 19m retest repro android13-5.15-lts report log
2024/03/05 02:05 14m retest repro android13-5.15-lts report log
Fix bisection attempts (1)
Created Duration User Patch Repo Result
2024/04/08 15:38 2h10m bisect fix android13-5.15-lts job log (0) log

Sample crash report:
BUG: scheduling while atomic: syz-executor225/372/0x00000002
Modules linked in:
Preemption disabled at:
[<ffffffff81ab934d>] spin_lock include/linux/spinlock.h:363 [inline]
[<ffffffff81ab934d>] preload_this_cpu_lock mm/vmalloc.c:1511 [inline]
[<ffffffff81ab934d>] alloc_vmap_area+0x22d/0x1a80 mm/vmalloc.c:1553
CPU: 1 PID: 372 Comm: syz-executor225 Not tainted 5.15.148-syzkaller-00718-g993bed180178 #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+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
 __ftrace_set_clr_event kernel/trace/trace_events.c:1050 [inline]
 trace_set_clr_event+0xcb/0x140 kernel/trace/trace_events.c:1116
 bpf_get_trace_printk_proto+0x22/0x80 kernel/trace/bpf_trace.c:411
 bpf_tracing_func_proto+0xb4/0x4a0 kernel/trace/bpf_trace.c:1073
 raw_tp_prog_func_proto+0x67/0x80 kernel/trace/bpf_trace.c:1520
 do_misc_fixups kernel/bpf/verifier.c:13278 [inline]
 bpf_check+0x9503/0x12bf0 kernel/bpf/verifier.c:14071
 bpf_prog_load+0x12ac/0x1b50 kernel/bpf/syscall.c:2327
 __sys_bpf+0x4bc/0x760 kernel/bpf/syscall.c:4627
 __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:0x7fc424063ee9
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:00007ffeef668628 EFLAGS: 00000246 ORIG_RAX: 0000000000000141
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fc424063ee9
RDX: 0000000000000048 RSI: 0000000020000b40 RDI: 0000000000000005
RBP: 00000000000f4240 R08: 0000000000000000 R09: 00000000000000a0
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000004cd8
R13: 00007ffeef66863c R14: 00007ffeef668650 R15: 00007ffeef668640
 </TASK>

Crashes (5):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/03/08 06:50 android13-5.15-lts 993bed180178 cf82cde1 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-android-5-15 BUG: scheduling while atomic in trace_set_clr_event
2024/02/20 02:05 android13-5.15-lts 993bed180178 3af7dd65 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-android-5-15 BUG: scheduling while atomic in trace_set_clr_event
2024/02/19 07:21 android13-5.15-lts 993bed180178 578f7538 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-android-5-15-perf BUG: scheduling while atomic in trace_set_clr_event
2024/02/19 06:02 android13-5.15-lts 993bed180178 578f7538 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-android-5-15 BUG: scheduling while atomic in trace_set_clr_event
2024/02/14 06:36 android13-5.15-lts 3802b45594e1 d902085f .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-android-5-15-perf BUG: scheduling while atomic in trace_set_clr_event
* Struck through repros no longer work on HEAD.