syzbot


WARNING: suspicious RCU usage in get_callchain_entry

Status: upstream: reported on 2025/06/18 02:15
Reported-by: syzbot+013fb58ec10bd119bf65@syzkaller.appspotmail.com
First crash: 5h55m, last: 5h55m
Similar bugs (3)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-5.15 WARNING: suspicious RCU usage in get_callchain_entry origin:upstream C 653 2h56m 369d 0/3 upstream: reported C repro on 2024/06/13 11:30
linux-6.1 WARNING: suspicious RCU usage in get_callchain_entry origin:upstream missing-backport C 742 1h13m 417d 0/3 upstream: reported C repro on 2024/04/26 10:45
upstream WARNING: suspicious RCU usage in get_callchain_entry perf C error 6247 4h46m 413d 0/28 upstream: reported C repro on 2024/04/30 10:49

Sample crash report:
=============================
WARNING: suspicious RCU usage
6.6.93-syzkaller #0 Not tainted
-----------------------------
kernel/events/callchain.c:161 suspicious rcu_dereference_check() usage!

other info that might help us debug this:


rcu_scheduler_active = 2, debug_locks = 1
1 lock held by syz.0.2979/23361:
 #0: ffffffff8cd2f900 (rcu_read_lock_trace){....}-{0:0}, at: rcu_lock_acquire include/linux/rcupdate.h:334 [inline]
 #0: ffffffff8cd2f900 (rcu_read_lock_trace){....}-{0:0}, at: rcu_read_lock_trace+0x37/0x70 include/linux/rcupdate_trace.h:57

stack backtrace:
CPU: 0 PID: 23361 Comm: syz.0.2979 Not tainted 6.6.93-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x16c/0x230 lib/dump_stack.c:106
 lockdep_rcu_suspicious+0x1e1/0x300 kernel/locking/lockdep.c:6731
 get_callchain_entry+0x2a9/0x3c0 kernel/events/callchain.c:161
 get_perf_callchain+0xa3/0x4b0 kernel/events/callchain.c:187
 __bpf_get_stack+0x2d7/0x510 kernel/bpf/stackmap.c:435
 ____bpf_get_stack_raw_tp kernel/trace/bpf_trace.c:1917 [inline]
 bpf_get_stack_raw_tp+0x195/0x220 kernel/trace/bpf_trace.c:1907
 bpf_prog_d43750871481577d+0x45/0x49
 bpf_dispatcher_nop_func include/linux/bpf.h:1213 [inline]
 __bpf_prog_run include/linux/filter.h:612 [inline]
 bpf_prog_run include/linux/filter.h:619 [inline]
 bpf_prog_run_pin_on_cpu+0x63/0x140 include/linux/filter.h:636
 bpf_prog_test_run_syscall+0x311/0x490 net/bpf/test_run.c:1501
 bpf_prog_test_run+0x321/0x390 kernel/bpf/syscall.c:4123
 __sys_bpf+0x440/0x800 kernel/bpf/syscall.c:5485
 __do_sys_bpf kernel/bpf/syscall.c:5571 [inline]
 __se_sys_bpf kernel/bpf/syscall.c:5569 [inline]
 __x64_sys_bpf+0x7c/0x90 kernel/bpf/syscall.c:5569
 do_syscall_x64 arch/x86/entry/common.c:51 [inline]
 do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
 entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f402758e929
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f40284e3038 EFLAGS: 00000246 ORIG_RAX: 0000000000000141
RAX: ffffffffffffffda RBX: 00007f40277b5fa0 RCX: 00007f402758e929
RDX: 0000000000000010 RSI: 0000200000000740 RDI: 000000000000000a
RBP: 00007f4027610b39 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f40277b5fa0 R15: 00007fff922e9ec8
 </TASK>

Crashes (3):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/06/18 02:15 linux-6.6.y c2603c511feb e77fae15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan WARNING: suspicious RCU usage in get_callchain_entry
2025/06/18 02:15 linux-6.6.y c2603c511feb e77fae15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan WARNING: suspicious RCU usage in get_callchain_entry
2025/06/18 02:14 linux-6.6.y c2603c511feb e77fae15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan WARNING: suspicious RCU usage in get_callchain_entry
* Struck through repros no longer work on HEAD.