WARNING: suspicious RCU usage in corrupted (3)

WARNING: suspicious RCU usage in corrupted (3)

Status: upstream: reported C repro on 2025/05/26 08:39
Subsystems: net
[Documentation on labels]
Reported-by: syzbot+9767c7ed68b95cfa69e6@syzkaller.appspotmail.com
First crash: 6d12h, last: 6d12h

Cause bisection: introduced by (bisect log) :
commit ee971630f20fd421fffcdc4543731ebcb54ed6d0
Author: Feng Yang <yangfeng@kylinos.cn>
Date: Tue May 6 06:14:33 2025 +0000

bpf: Allow some trace helpers for all prog types

Crash: WARNING: suspicious RCU usage in task_cls_state (log)
Repro: C syz .config

▶ ▼ Discussions (2)

Title	Replies (including bot)	Last reply
[PATCH bpf-next v1 1/2] bpf: Restrict usage scope of bpf_get_cgroup_classid	2 (2)	2025/05/29 16:46
[syzbot] [net?] WARNING: suspicious RCU usage in corrupted (3)	0 (1)	2025/05/26 08:39

▶ ▼ Similar bugs (2)

Kernel	Title	Repro	Cause bisect	Fix bisect	Count	Last	Reported	Patched	Status
upstream	WARNING: suspicious RCU usage in corrupted kernel	syz	error		1	2578d	2578d	0/28	closed as invalid on 2019/04/08 15:02
upstream	WARNING: suspicious RCU usage in corrupted (2) net	C	unreliable		7	1071d	1082d	22/28	fixed on 2023/02/24 13:50

Sample crash report:

=============================
WARNING: suspicious RCU usage
6.15.0-rc4-syzkaller-g079e5c56a5c4 #0 Not tainted
-----------------------------
net/core/netclassid_cgroup.c:24 suspicious rcu_dereference_check() usage!

other info that might help us debug this:


rcu_scheduler_active = 2,

Crashes (1):
Time	Kernel	Commit	Syzkaller	Config	Log	Report	Syz repro	C repro	VM info	Assets (help?)	Manager	Title
2025/05/24 19:56	bpf-next	079e5c56a5c4	ed351ea7	.config	console log	report	syz / log	C		[disk image] [vmlinux] [kernel image]	ci-upstream-bpf-next-kasan-gce	WARNING: suspicious RCU usage in corrupted

* ~~Struck through~~ repros no longer work on HEAD.