syzbot


BUG: workqueue leaked atomic, lock or RCU: kworker/NUM:NUM[NUM]

Status: upstream: reported on 2024/10/21 08:36
Subsystems: kernel
[Documentation on labels]
Reported-by: syzbot+21814e89fd126bbfb79c@syzkaller.appspotmail.com
First crash: 71d, last: 5d04h
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [kernel?] BUG: workqueue leaked atomic, lock or RCU: kworker/NUM:NUM[NUM] 0 (1) 2024/10/21 08:36

Sample crash report:
BUG: workqueue leaked atomic, lock or RCU: kworker/0:4[5280]
     preempt=0x00000000 lock=0->0 RCU=0->0 workfn=nsim_dev_trap_report_work
INFO: lockdep is turned off.
CPU: 0 UID: 0 PID: 5280 Comm: kworker/0:4 Not tainted 6.12.0-rc1-syzkaller-00360-g09cf85ef183a #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
Workqueue: events nsim_dev_trap_report_work

Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:94 [inline]
 dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120
 process_one_work kernel/workqueue.c:3250 [inline]
 process_scheduled_works+0x1158/0x1850 kernel/workqueue.c:3310
 worker_thread+0x870/0xd30 kernel/workqueue.c:3391
 kthread+0x2f0/0x390 kernel/kthread.c:389
 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
 </TASK>

Crashes (2):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/10/10 20:54 net-next 09cf85ef183a 8fbfc0c8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce BUG: workqueue leaked atomic, lock or RCU: kworker/NUM:NUM[NUM]
2024/12/16 07:55 https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing d8d936c51388 7cbfbb3a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-usb BUG: workqueue leaked atomic, lock or RCU: kworker/NUM:NUM[NUM]
* Struck through repros no longer work on HEAD.