syzbot


BUG: scheduling while atomic in rcu_barrier

Status: premoderation: reported on 2024/04/05 16:00
Reported-by: syzbot+024d4fc8b96f656dd9fa@syzkaller.appspotmail.com
First crash: 70d, last: 70d

Sample crash report:
BUG: scheduling while atomic: kworker/u4:6/946/0x00000002
Modules linked in:
Preemption disabled at:
[<ffffffff8145ef61>] irq_enter_rcu+0x11/0x80 kernel/softirq.c:659
CPU: 0 PID: 946 Comm: kworker/u4:6 Not tainted 6.1.75-syzkaller-00123-g60534eef4739 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
Workqueue: netns cleanup_net
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x151/0x1b7 lib/dump_stack.c:106
 dump_stack+0x15/0x1b lib/dump_stack.c:113
 __schedule_bug+0x195/0x260 kernel/sched/core.c:5960
 schedule_debug kernel/sched/core.c:5987 [inline]
 __schedule+0xcf7/0x1550 kernel/sched/core.c:6622
 schedule+0xc3/0x180 kernel/sched/core.c:6805
 schedule_preempt_disabled+0x13/0x20 kernel/sched/core.c:6864
 mutex_optimistic_spin kernel/locking/mutex.c:529 [inline]
 __mutex_lock_common kernel/locking/mutex.c:629 [inline]
 __mutex_lock+0x5b6/0x1ca0 kernel/locking/mutex.c:774
 __mutex_lock_slowpath+0xe/0x10 kernel/locking/mutex.c:1063
 mutex_lock+0x130/0x1e0 kernel/locking/mutex.c:295
 rcu_barrier+0x49/0x5f0 kernel/rcu/tree.c:4041
 cleanup_net+0x8fa/0xbf0 net/core/net_namespace.c:612
 process_one_work+0x73d/0xcb0 kernel/workqueue.c:2299
 worker_thread+0xa60/0x1260 kernel/workqueue.c:2446
 kthread+0x26d/0x300 kernel/kthread.c:386
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
 </TASK>

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/04/05 15:59 android14-6.1 60534eef4739 77230c29 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-6-1-perf BUG: scheduling while atomic in rcu_barrier
* Struck through repros no longer work on HEAD.