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

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: c79648372d02 Linux 5.15.189
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1585a782580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f3b1215b3cf4119f
dashboard link: https://syzkaller.appspot.com/bug?extid=db84c307ff5a2a670ffd
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/fa511d2a8893/disk-c7964837.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f14b6c77bbb9/vmlinux-c7964837.xz
kernel image: https://storage.googleapis.com/syzbot-assets/388987ba15c6/bzImage-c7964837.xz

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

(syz.3.13,4361,1):__ocfs2_flush_truncate_log:6056 ERROR: status = -30
(syz.3.13,4361,1):ocfs2_try_to_free_truncate_log:6136 ERROR: status = -30
(syz.3.13,4361,1):ocfs2_write_begin_nolock:1876 ERROR: status = -30
================================================
WARNING: lock held when returning to user space!
5.15.189-syzkaller #0 Not tainted
------------------------------------------------
syz.3.13/4361 is leaving the kernel with locks still held!
3 locks held by syz.3.13/4361:
#0: ffff888078c7c650 (sb_internal#2){.+.+}-{0:0}, at: ocfs2_replay_truncate_records fs/ocfs2/alloc.c:5939 [inline]
#0: ffff888078c7c650 (sb_internal#2){.+.+}-{0:0}, at: __ocfs2_flush_truncate_log+0x46a/0x1060 fs/ocfs2/alloc.c:6053
#1: ffff8880636b74e8 (&journal->j_trans_barrier){.+.+}-{3:3}, at: ocfs2_start_trans+0x368/0x6c0 fs/ocfs2/journal.c:374
#2: ffff88807d536990 (jbd2_handle){++++}-{0:0}, at: start_this_handle+0x1312/0x15a0 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

[syzbot]

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