syzbot


BUG: workqueue leaked lock or atomic in free_work

Status: upstream: reported C repro on 2024/02/10 00:41
Bug presence: origin:lts
[Documentation on labels]
Reported-by: syzbot+7a03a760f641ac52987b@syzkaller.appspotmail.com
First crash: 125d, last: 47d
Bug presence (2)
Date Name Commit Repro Result
2024/02/10 lts (merge base) ba6f5fb46511 C [report] BUG: scheduling while atomic in exit_to_user_mode_loop
2024/02/10 upstream (ToT) 9ed18b0b7765 C Didn't crash
Last patch testing requests (2)
Created Duration User Patch Repo Result
2024/05/11 18:27 9m retest repro android14-6.1 report log
2024/02/24 00:41 7m retest repro android14-6.1 report log

Sample crash report:
BUG: workqueue leaked lock or atomic: kworker/1:2/0x00000001/824
     last function: free_work
CPU: 1 PID: 824 Comm: kworker/1:2 Not tainted 6.1.68-syzkaller-00008-gd3f73f04529a #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023
Workqueue: events free_work
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
 process_one_work+0x94e/0xcb0 kernel/workqueue.c:2314
 worker_thread+0xa60/0x1260 kernel/workqueue.c:2446
 kthread+0x26d/0x300 kernel/kthread.c:376
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
 </TASK>
BUG: scheduling while atomic: kworker/1:2/824/0x00000002
Modules linked in:
Preemption disabled at:
[<ffffffff81b65ac6>] spin_lock include/linux/spinlock.h:350 [inline]
[<ffffffff81b65ac6>] free_vmap_area_noflush+0x226/0xa30 mm/vmalloc.c:1837
CPU: 1 PID: 824 Comm: kworker/1:2 Not tainted 6.1.68-syzkaller-00008-gd3f73f04529a #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023
Workqueue:  0x0 (events)
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+0xce9/0x1540 kernel/sched/core.c:6622
 schedule+0xc3/0x180 kernel/sched/core.c:6805
 worker_thread+0xefa/0x1260 kernel/workqueue.c:2467
 kthread+0x26d/0x300 kernel/kthread.c:376
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
 </TASK>

Crashes (5):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/02/10 00:40 android14-6.1 d3f73f04529a 77b23aa1 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-android-6-1-perf BUG: workqueue leaked lock or atomic in free_work
2024/04/27 18:24 android14-6.1 fa87a072a7fc 07b455f9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-6-1 BUG: workqueue leaked lock or atomic in free_work
2024/04/22 18:43 android14-6.1 503add184388 36c961ad .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-6-1 BUG: workqueue leaked lock or atomic in free_work
2024/04/14 09:42 android14-6.1 cfa154389a65 c8349e48 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-6-1-perf BUG: workqueue leaked lock or atomic in free_work
2024/03/24 08:43 android14-6.1 d518ca9dbbe9 0ea90952 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-6-1 BUG: workqueue leaked lock or atomic in free_work
* Struck through repros no longer work on HEAD.