[v5.15] WARNING: lock held when returning to user space in __ocfs2_flush_truncate_log (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 3330a8d33e08 Linux 5.15.201
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=147ecd5a580000
kernel config: https://syzkaller.appspot.com/x/.config?x=353ae28c40b35af5
dashboard link: https://syzkaller.appspot.com/bug?extid=8de411ce7790770fb427
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/b65fe19af112/disk-3330a8d3.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/351948519a0d/vmlinux-3330a8d3.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a3b3f8477595/bzImage-3330a8d3.xz

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

(syz.3.131,4878,0):ocfs2_replay_truncate_records:5974 ERROR: status = -30
(syz.3.131,4878,0):__ocfs2_flush_truncate_log:6055 ERROR: status = -30
(syz.3.131,4878,0):ocfs2_try_to_free_truncate_log:6135 ERROR: status = -30
(syz.3.131,4878,0):ocfs2_write_begin_nolock:1876 ERROR: status = -30
================================================
WARNING: lock held when returning to user space!
syzkaller #0 Not tainted
------------------------------------------------
syz.3.131/4878 is leaving the kernel with locks still held!
3 locks held by syz.3.131/4878:
#0: ffff8880232a0650 (sb_internal#4){.+.+}-{0:0}, at: ocfs2_replay_truncate_records fs/ocfs2/alloc.c:5938 [inline]
#0: ffff8880232a0650 (sb_internal#4){.+.+}-{0:0}, at: __ocfs2_flush_truncate_log+0x4a5/0x1110 fs/ocfs2/alloc.c:6052
#1: ffff888061e4b8e8 (&journal->j_trans_barrier){.+.+}-{3:3}, at: ocfs2_start_trans+0x3a6/0x6f0 fs/ocfs2/journal.c:374
#2: ffff888060e76990 (jbd2_handle){++++}-{0:0}, at: start_this_handle+0x134c/0x15c0 fs/jbd2/transaction.c:462


---
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