WARNING: suspicious RCU usage in corrupted

WARNING: suspicious RCU usage in corrupted

Status: closed as invalid on 2019/04/08 15:02
Subsystems: kernel
[Documentation on labels]
Reported-by: syzbot+5cec30d9329f61f2fb29@syzkaller.appspotmail.com
First crash: 2568d, last: 2568d

Cause bisection: failed (error log, bisect log)

▶ ▼ Discussions (1)

Title	Replies (including bot)	Last reply
WARNING: suspicious RCU usage in corrupted	1 (2)	2019/04/08 15:02

▶ ▼ Similar bugs (1)

Kernel	Title	Repro	Cause bisect	Fix bisect	Count	Last	Reported	Patched	Status
upstream	WARNING: suspicious RCU usage in corrupted (2) net	C	unreliable		7	1060d	1071d	22/28	fixed on 2023/02/24 13:50

Sample crash report:

random: sshd: uninitialized urandom read (32 bytes read)
random: sshd: uninitialized urandom read (32 bytes read)
IPVS: ftp: loaded support on port[0] = 21

=============================
WARNING: suspicious RCU usage
4.17.0-rc4+ #64 Not tainted
-----------------------------
arch/x86/kernel/traps.c:537 entry code didn't wake RCU!

other info that might help us debug this:


RCU used illegally from idle CPU!
rcu_scheduler_active = 2, debug_locks = 1
RCU used illegally from extended quiescent state!
no locks held by swapper/0/0.

stack backtrace:

Crashes (1):
Time	Kernel	Commit	Syzkaller	Config	Log	Report	Syz repro	C repro	VM info	Assets (help?)	Manager	Title
2018/05/09 14:17	upstream	036db8bd9637	12c7428a	.config	console log	report	syz				ci-upstream-kasan-gce-386

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