[v5.15] BUG: workqueue leaked lock or atomic in ocfs2_truncate_log_worker

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 0c935c049b5c Linux 5.15.179
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1457d83f980000
kernel config: https://syzkaller.appspot.com/x/.config?x=98c228fbc016eb3a
dashboard link: https://syzkaller.appspot.com/bug?extid=308b761b4bf510188d07
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/d5477072f336/disk-0c935c04.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/77d15907ffb3/vmlinux-0c935c04.xz
kernel image: https://storage.googleapis.com/syzbot-assets/efe5d79cb16a/Image-0c935c04.gz.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+308b76...@syzkaller.appspotmail.com

(kworker/u4:12,4444,1):ocfs2_replay_truncate_records:5967 ERROR: status = -30
(kworker/u4:12,4444,0):__ocfs2_flush_truncate_log:6048 ERROR: status = -30
(kworker/u4:12,4444,0):ocfs2_truncate_log_worker:6082 ERROR: status = -30
BUG: workqueue leaked lock or atomic: kworker/u4:12/0x00000000/4444
last function: ocfs2_truncate_log_worker
3 locks held by kworker/u4:12/4444:
#0: ffff0000e6fbe650 (sb_internal#4){.+.+}-{0:0}, at: ocfs2_replay_truncate_records fs/ocfs2/alloc.c:5931 [inline]
#0: ffff0000e6fbe650 (sb_internal#4){.+.+}-{0:0}, at: __ocfs2_flush_truncate_log+0x414/0x10f0 fs/ocfs2/alloc.c:6045
#1: ffff0000d61da4e8 (&journal->j_trans_barrier){.+.+}-{3:3}, at: ocfs2_start_trans+0x45c/0x804 fs/ocfs2/journal.c:352
#2: ffff0000e73f2990 (jbd2_handle){++++}-{0:0}, at: start_this_handle+0xf98/0x12a4 fs/jbd2/transaction.c:462
CPU: 0 PID: 4444 Comm: kworker/u4:12 Not tainted 5.15.179-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
Workqueue: ocfs2_wq ocfs2_truncate_log_worker
Call trace:
dump_backtrace+0x0/0x530 arch/arm64/kernel/stacktrace.c:152
show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:216
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x108/0x170 lib/dump_stack.c:106
dump_stack+0x1c/0x58 lib/dump_stack.c:113
process_one_work+0xb7c/0x11b8 kernel/workqueue.c:2325
worker_thread+0x910/0x1034 kernel/workqueue.c:2457
kthread+0x37c/0x45c kernel/kthread.c:334
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:870
BUG: workqueue leaked lock or atomic: kworker/u4:12/0x00000000/4444
last function: ieee80211_scan_work
3 locks held by kworker/u4:12/4444:
#0: ffff0000e6fbe650 (sb_internal#4){.+.+}-{0:0}, at: ocfs2_replay_truncate_records fs/ocfs2/alloc.c:5931 [inline]
#0: ffff0000e6fbe650 (sb_internal#4){.+.+}-{0:0}, at: __ocfs2_flush_truncate_log+0x414/0x10f0 fs/ocfs2/alloc.c:6045
#1: ffff0000d61da4e8 (&journal->j_trans_barrier){.+.+}-{3:3}, at: ocfs2_start_trans+0x45c/0x804 fs/ocfs2/journal.c:352
#2: ffff0000e73f2990 (jbd2_handle){++++}-{0:0}, at: start_this_handle+0xf98/0x12a4 fs/jbd2/transaction.c:462
CPU: 0 PID: 4444 Comm: kworker/u4:12 Not tainted 5.15.179-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
Workqueue: phy15 ieee80211_scan_work
Call trace:
dump_backtrace+0x0/0x530 arch/arm64/kernel/stacktrace.c:152
show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:216
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x108/0x170 lib/dump_stack.c:106
dump_stack+0x1c/0x58 lib/dump_stack.c:113
process_one_work+0xb7c/0x11b8 kernel/workqueue.c:2325
worker_thread+0x910/0x1034 kernel/workqueue.c:2457
kthread+0x37c/0x45c kernel/kthread.c:334
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:870
BUG: workqueue leaked lock or atomic: kworker/u4:12/0x00000000/4444
last function: ieee80211_iface_work
3 locks held by kworker/u4:12/4444:
#0: ffff0000e6fbe650 (sb_internal#4){.+.+}-{0:0}, at: ocfs2_replay_truncate_records fs/ocfs2/alloc.c:5931 [inline]
#0: ffff0000e6fbe650 (sb_internal#4){.+.+}-{0:0}, at: __ocfs2_flush_truncate_log+0x414/0x10f0 fs/ocfs2/alloc.c:6045
#1: ffff0000d61da4e8 (&journal->j_trans_barrier){.+.+}-{3:3}, at: ocfs2_start_trans+0x45c/0x804 fs/ocfs2/journal.c:352
#2: ffff0000e73f2990 (jbd2_handle){++++}-{0:0}, at: start_this_handle+0xf98/0x12a4 fs/jbd2/transaction.c:462
CPU: 1 PID: 4444 Comm: kworker/u4:12 Not tainted 5.15.179-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
Workqueue: phy17 ieee80211_iface_work
Call trace:
dump_backtrace+0x0/0x530 arch/arm64/kernel/stacktrace.c:152
show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:216
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x108/0x170 lib/dump_stack.c:106
dump_stack+0x1c/0x58 lib/dump_stack.c:113
process_one_work+0xb7c/0x11b8 kernel/workqueue.c:2325
worker_thread+0x910/0x1034 kernel/workqueue.c:2457
kthread+0x37c/0x45c kernel/kthread.c:334
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:870
BUG: workqueue leaked lock or atomic: kworker/u4:12/0x00000000/4444
last function: ieee80211_iface_work
3 locks held by kworker/u4:12/4444:
#0: ffff0000e6fbe650 (sb_internal#4){.+.+}-{0:0}, at: ocfs2_replay_truncate_records fs/ocfs2/alloc.c:5931 [inline]
#0: ffff0000e6fbe650 (sb_internal#4){.+.+}-{0:0}, at: __ocfs2_flush_truncate_log+0x414/0x10f0 fs/ocfs2/alloc.c:6045
#1: ffff0000d61da4e8 (&journal->j_trans_barrier){.+.+}-{3:3}, at: ocfs2_start_trans+0x45c/0x804 fs/ocfs2/journal.c:352
#2: ffff0000e73f2990 (jbd2_handle){++++}-{0:0}, at: start_this_handle+0xf98/0x12a4 fs/jbd2/transaction.c:462
CPU: 0 PID: 4444 Comm: kworker/u4:12 Not tainted 5.15.179-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
Workqueue: phy17 ieee80211_iface_work
Call trace:
dump_backtrace+0x0/0x530 arch/arm64/kernel/stacktrace.c:152
show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:216
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x108/0x170 lib/dump_stack.c:106
dump_stack+0x1c/0x58 lib/dump_stack.c:113
process_one_work+0xb7c/0x11b8 kernel/workqueue.c:2325
worker_thread+0x910/0x1034 kernel/workqueue.c:2457
kthread+0x37c/0x45c kernel/kthread.c:334
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:870
BUG: workqueue leaked lock or atomic: kworker/u4:12/0x00000000/4444
last function: ieee80211_iface_work
3 locks held by kworker/u4:12/4444:
#0: ffff0000e6fbe650 (sb_internal#4){.+.+}-{0:0}, at: ocfs2_replay_truncate_records fs/ocfs2/alloc.c:5931 [inline]
#0: ffff0000e6fbe650 (sb_internal#4){.+.+}-{0:0}, at: __ocfs2_flush_truncate_log+0x414/0x10f0 fs/ocfs2/alloc.c:6045
#1: ffff0000d61da4e8 (&journal->j_trans_barrier){.+.+}-{3:3}, at: ocfs2_start_trans+0x45c/0x804 fs/ocfs2/journal.c:352
#2: ffff0000e73f2990 (jbd2_handle){++++}-{0:0}, at: start_this_handle+0xf98/0x12a4 fs/jbd2/transaction.c:462
CPU: 0 PID: 4444 Comm: kworker/u4:12 Not tainted 5.15.179-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
Workqueue: phy17 ieee80211_iface_work
Call trace:
dump_backtrace+0x0/0x530 arch/arm64/kernel/stacktrace.c:152
show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:216
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x108/0x170 lib/dump_stack.c:106
dump_stack+0x1c/0x58 lib/dump_stack.c:113
process_one_work+0xb7c/0x11b8 kernel/workqueue.c:2325
worker_thread+0x910/0x1034 kernel/workqueue.c:2457
kthread+0x37c/0x45c kernel/kthread.c:334
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:870

======================================================


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.