syzbot


WARNING: suspicious RCU usage in __schedule

Status: closed as dup on 2021/04/13 18:11
Subsystems: kernel
[Documentation on labels]
Reported-by: syzbot+be81a058b10931003a4a@syzkaller.appspotmail.com
First crash: 1336d, last: 1251d
Duplicate of
Title Repro Cause bisect Fix bisect Count Last Reported
WARNING: suspicious RCU usage in getname_flags fs 2 1240d 1331d
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] WARNING: suspicious RCU usage in __schedule 1 (2) 2021/04/13 18:11
Similar bugs (1)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream WARNING: suspicious RCU usage in __schedule (2) perf 1 224d 220d 0/28 auto-obsoleted due to no activity on 2024/07/23 19:40

Sample crash report:
=============================
WARNING: suspicious RCU usage
5.13.0-rc7-syzkaller #0 Not tainted
-----------------------------
kernel/sched/core.c:4912 Illegal context switch in RCU-sched read-side critical section!

other info that might help us debug this:


rcu_scheduler_active = 2, debug_locks = 0
no locks held by syz-executor.5/8841.

stack backtrace:
CPU: 1 PID: 8841 Comm: syz-executor.5 Not tainted 5.13.0-rc7-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
 __dump_stack lib/dump_stack.c:79 [inline]
 dump_stack+0x141/0x1d7 lib/dump_stack.c:120
 schedule_debug kernel/sched/core.c:4912 [inline]
 __schedule+0x1647/0x23e0 kernel/sched/core.c:5038
 schedule+0xcf/0x270 kernel/sched/core.c:5226
 freezable_schedule include/linux/freezer.h:172 [inline]
 do_nanosleep+0x268/0x6a0 kernel/time/hrtimer.c:1896
 hrtimer_nanosleep+0x1f9/0x4a0 kernel/time/hrtimer.c:1949
 common_nsleep+0xa2/0xc0 kernel/time/posix-timers.c:1227
 __do_sys_clock_nanosleep kernel/time/posix-timers.c:1267 [inline]
 __se_sys_clock_nanosleep kernel/time/posix-timers.c:1245 [inline]
 __x64_sys_clock_nanosleep+0x2f4/0x430 kernel/time/posix-timers.c:1245
 do_syscall_64+0x3a/0xb0 arch/x86/entry/common.c:47
 entry_SYSCALL_64_after_hwframe+0x44/0xae
RIP: 0033:0x48a7a1
Code: 24 0c 89 3c 24 48 89 4c 24 18 e8 aa e7 ff ff 4c 8b 54 24 18 48 8b 54 24 10 41 89 c0 8b 74 24 0c 8b 3c 24 b8 e6 00 00 00 0f 05 <44> 89 c7 48 89 04 24 e8 e3 e7 ff ff 48 8b 04 24 eb 97 66 2e 0f 1f
RSP: 002b:00007fff72a13d70 EFLAGS: 00000293
 ORIG_RAX: 00000000000000e6
RAX: ffffffffffffffda RBX: 0000000000000010 RCX: 000000000048a7a1
RDX: 00007fff72a13db0 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 00007fff72a13e4c R08: 0000000000000000 R09: 00007fff72bc8080
R10: 0000000000000000 R11: 0000000000000293 R12: 0000000000000032
R13: 000000000003b8f5 R14: 0000000000000013 R15: 00007fff72a13eb0

Crashes (5):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2021/06/23 16:47 upstream 0c18f29aae7c aba2b2fb .config console log report info ci-upstream-kasan-gce-selinux-root WARNING: suspicious RCU usage in __schedule
2021/05/07 13:41 upstream d2b6f8a17919 f6da8120 .config console log report info ci-upstream-kasan-gce-root WARNING: suspicious RCU usage in __schedule
2021/05/02 08:45 upstream d2b6f8a17919 77e2b668 .config console log report info ci-upstream-kasan-gce WARNING: suspicious RCU usage in __schedule
2021/03/30 08:09 upstream 1e43c377a79f 6a81331a .config console log report info ci-qemu2-arm64-compat WARNING: suspicious RCU usage in __schedule
2021/05/06 17:26 linux-next 23c498428c14 06585184 .config console log report info ci-upstream-linux-next-kasan-gce-root WARNING: suspicious RCU usage in __schedule
* Struck through repros no longer work on HEAD.