syzbot


BUG: workqueue leaked lock or atomic in ext4_end_io_rsv_work

Status: auto-obsoleted due to no activity on 2024/07/19 03:24
Reported-by: syzbot+de8d91937a2b359c224e@syzkaller.appspotmail.com
First crash: 243d, last: 217d

Sample crash report:
BUG: workqueue leaked lock or atomic: kworker/u4:2/0x00000001/45
     last function: ext4_end_io_rsv_work
CPU: 1 PID: 45 Comm: kworker/u4:2 Not tainted 5.15.148-syzkaller-00013-gad06eaf051cd #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
Workqueue: ext4-rsv-conversion ext4_end_io_rsv_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/0x17 lib/dump_stack.c:113
 process_one_work+0x8d8/0xc10 kernel/workqueue.c:2340
 worker_thread+0xad5/0x12a0 kernel/workqueue.c:2472
 kthread+0x421/0x510 kernel/kthread.c:337
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
 </TASK>
BUG: workqueue leaked lock or atomic: kworker/u4:2/0x00000001/45
     last function: wb_update_bandwidth_workfn
CPU: 1 PID: 45 Comm: kworker/u4:2 Not tainted 5.15.148-syzkaller-00013-gad06eaf051cd #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
Workqueue: writeback wb_update_bandwidth_workfn
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
 process_one_work+0x8d8/0xc10 kernel/workqueue.c:2340
 worker_thread+0xad5/0x12a0 kernel/workqueue.c:2472
 kthread+0x421/0x510 kernel/kthread.c:337
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
 </TASK>
BUG: scheduling while atomic: kworker/u4:2/45/0x00000002
Modules linked in:
Preemption disabled at:
[<ffffffff819a4e9a>] test_clear_page_writeback+0x26a/0x8a0 mm/page-writeback.c:2786
CPU: 1 PID: 45 Comm: kworker/u4:2 Not tainted 5.15.148-syzkaller-00013-gad06eaf051cd #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
Workqueue:  0x0 (writeback)
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
 worker_thread+0xf7f/0x12a0 kernel/workqueue.c:2493
 kthread+0x421/0x510 kernel/kthread.c:337
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
 </TASK>
device bridge_slave_1 left promiscuous mode
bridge0: port 2(bridge_slave_1) entered disabled state
device bridge_slave_0 left promiscuous mode
bridge0: port 1(bridge_slave_0) entered disabled state
device veth1_macvtap left promiscuous mode
device veth0_vlan left promiscuous mode
device bridge_slave_1 left promiscuous mode
bridge0: port 2(bridge_slave_1) entered disabled state
device bridge_slave_0 left promiscuous mode
bridge0: port 1(bridge_slave_0) entered disabled state
device veth1_macvtap left promiscuous mode

Crashes (4):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/04/20 03:13 android13-5.15-lts ad06eaf051cd af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-15-perf BUG: workqueue leaked lock or atomic in ext4_end_io_rsv_work
2024/04/15 15:10 android13-5.15-lts ad06eaf051cd b9af7e61 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-15-perf BUG: workqueue leaked lock or atomic in ext4_end_io_rsv_work
2024/03/27 04:33 android13-5.15-lts 993bed180178 454571b6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-15 BUG: workqueue leaked lock or atomic in ext4_end_io_rsv_work
2024/03/24 15:48 android13-5.15-lts 993bed180178 0ea90952 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-15-perf BUG: workqueue leaked lock or atomic in ext4_end_io_rsv_work
* Struck through repros no longer work on HEAD.