syzbot


BUG: scheduling while atomic in rcu_boost_kthread

Status: auto-obsoleted due to no activity on 2024/07/09 21:44
Bug presence: origin:lts
Labels: missing-backport
[Documentation on labels]
Reported-by: syzbot+a5c9a3b6200924289673@syzkaller.appspotmail.com
First crash: 145d, last: 100d
Fix bisection: fixed by (bisect log) :
commit 4b349c55bbd33c8918dbac13876d6842af571505
Author: Jiri Olsa <jolsa@kernel.org>
Date: Sat Feb 17 12:13:20 2024 +0000

  bpf: Do cleanup in bpf_bprintf_cleanup only when needed

  
Bug presence (4)
Date Name Commit Repro Result
2024/04/10 android13-5.15-lts (ToT) 993bed180178 C [report] BUG: scheduling while atomic in rcu_boost_kthread
2024/02/25 lts (merge base) 6139f2a02fe0 C [report] BUG: scheduling while atomic in rcu_boost_kthread
2024/04/10 lts (merge base) 6139f2a02fe0 C Didn't crash
2024/02/25 upstream (ToT) ab0a97cffa0b C Didn't crash
Similar bugs (1)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
android-6-1 BUG: scheduling while atomic in rcu_boost_kthread origin:lts C 3 25d 153d 0/2 upstream: reported C repro on 2024/02/17 15:42
Last patch testing requests (1)
Created Duration User Patch Repo Result
2024/03/10 15:41 17m retest repro android13-5.15-lts report log

Sample crash report:
BUG: scheduling while atomic: rcub/0/15/0x00000002
Modules linked in:
Preemption disabled at:
[<ffffffff84c71428>] schedule+0x118/0x1e0 kernel/sched/core.c:6594
CPU: 1 PID: 15 Comm: rcub/0 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
 rt_mutex_slowlock_block+0xef/0x5a0 kernel/locking/rtmutex.c:1561
 __rt_mutex_slowlock kernel/locking/rtmutex.c:1628 [inline]
 __rt_mutex_slowlock_locked kernel/locking/rtmutex.c:1661 [inline]
 rt_mutex_slowlock+0x184/0x2f0 kernel/locking/rtmutex.c:1690
 __rt_mutex_lock kernel/locking/rtmutex.c:1702 [inline]
 __rt_mutex_lock_common kernel/locking/rtmutex_api.c:30 [inline]
 rt_mutex_lock+0x14a/0x210 kernel/locking/rtmutex_api.c:66
 rcu_boost kernel/rcu/tree_plugin.h:1060 [inline]
 rcu_boost_kthread+0x231/0x6e0 kernel/rcu/tree_plugin.h:1085
 kthread+0x421/0x510 kernel/kthread.c:337
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
 </TASK>

Crashes (3):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/02/25 15:34 android13-5.15-lts 993bed180178 8d446f15 .config strace log report syz [disk image] [vmlinux] [kernel image] ci2-android-5-15 BUG: scheduling while atomic in rcu_boost_kthread
2024/03/12 06:31 android13-5.15-lts 993bed180178 6ee49f2e .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-15-perf BUG: scheduling while atomic in rcu_boost_kthread
2024/03/11 07:42 android13-5.15-lts 993bed180178 6ee49f2e .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-15 BUG: scheduling while atomic in rcu_boost_kthread
* Struck through repros no longer work on HEAD.