[v6.6] WARNING in ocfs2_journal_toggle_dirty

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 79643295eba1 Linux 6.6.157
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=128f9005580000
kernel config: https://syzkaller.appspot.com/x/.config?x=7be9809cedd6b69c
dashboard link: https://syzkaller.appspot.com/bug?extid=0338bfd85ef4734ebe98
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=149c6805580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/a1af8d16581c/disk-79643295.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/66be9bddb1ec/vmlinux-79643295.xz
kernel image: https://storage.googleapis.com/syzbot-assets/0329b316645d/bzImage-79643295.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/ac416f6a5905/mount_0.gz
fsck result: OK (log: https://syzkaller.appspot.com/x/fsck.log?x=148f9005580000)

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

(syz.0.350,7269,0):ocfs2_assign_bh:2416 ERROR: status = -5
(syz.0.350,7269,0):ocfs2_inode_lock_full_nested:2511 ERROR: status = -5
(syz.0.350,7269,0):ocfs2_shutdown_local_alloc:411 ERROR: status = -5
------------[ cut here ]------------
WARNING: CPU: 0 PID: 7269 at fs/ocfs2/journal.c:1034 ocfs2_journal_toggle_dirty+0x300/0x360 fs/ocfs2/journal.c:1034
Modules linked in:
CPU: 0 PID: 7269 Comm: syz.0.350 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
RIP: 0010:ocfs2_journal_toggle_dirty+0x300/0x360 fs/ocfs2/journal.c:1034
Code: 8b e8 14 99 13 00 43 c6 44 27 04 f8 e9 47 ff ff ff e8 54 bc 23 fe e9 3d ff ff ff e8 4a bc 23 fe e9 33 ff ff ff e8 40 bc 23 fe <0f> 0b bb fb ff ff ff 49 bc 00 00 00 00 00 fc ff df 4c 8b 7c 24 20
RSP: 0000:ffffc90003936f60 EFLAGS: 00010293
RAX: ffffffff8363cf10 RBX: 1ffff1100b8bfa22 RCX: ffff88802743bc00
RDX: 0000000000000000 RSI: 00000000ffffffff RDI: 0000000000000000
RBP: ffffc90003937030 R08: ffffffff911eb617 R09: 1ffffffff223d6c2
R10: dffffc0000000000 R11: fffffbfff223d6c3 R12: 00000000ffffffff
R13: ffff8880543cfa00 R14: ffff888021fa5800 R15: 0000000000000000
FS: 00007f5aa83fe6c0(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fb119849000 CR3: 000000001c32f000 CR4: 00000000003506f0
Call Trace:
<TASK>
ocfs2_journal_shutdown+0x541/0xaf0 fs/ocfs2/journal.c:1117
ocfs2_mount_volume+0x1393/0x1510 fs/ocfs2/super.c:1841
ocfs2_fill_super+0x35fd/0x5010 fs/ocfs2/super.c:1084
mount_bdev+0x21c/0x2c0 fs/super.c:1651
legacy_get_tree+0xea/0x180 fs/fs_context.c:662
vfs_get_tree+0x8c/0x280 fs/super.c:1772
do_new_mount+0x24a/0xa40 fs/namespace.c:3386
do_mount fs/namespace.c:3726 [inline]
__do_sys_mount fs/namespace.c:3935 [inline]
__se_sys_mount+0x2e7/0x3d0 fs/namespace.c:3912
do_syscall_x64 arch/x86/entry/common.c:46 [inline]
do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:76
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f5aa8d9f3ca
Code: 48 c7 c2 e8 ff ff ff f7 d8 64 89 02 b8 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f5aa83fde58 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f5aa83fdee0 RCX: 00007f5aa8d9f3ca
RDX: 00002000000026c0 RSI: 0000200000004780 RDI: 00007f5aa83fdea0
RBP: 00002000000026c0 R08: 00007f5aa83fdee0 R09: 0000000002010080
R10: 0000000002010080 R11: 0000000000000246 R12: 0000200000004780
R13: 00007f5aa83fdea0 R14: 0000000000004703 R15: 0000200000000480
</TASK>


---
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 syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

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