[v6.6] kernel BUG in ocfs2_journal_toggle_dirty

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 4791134e4aeb Linux 6.6.118
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=16418992580000
kernel config: https://syzkaller.appspot.com/x/.config?x=12606d4b8832c7e4
dashboard link: https://syzkaller.appspot.com/bug?extid=62c442becc6789f0ae17
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12bc821a580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=141ef6b4580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/ca168ecfe887/disk-4791134e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/adda86b1a76b/vmlinux-4791134e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/cc2019969cb7/bzImage-4791134e.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/f8e379dd90a6/mount_0.gz
fsck result: OK (log: https://syzkaller.appspot.com/x/fsck.log?x=101ef6b4580000)

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

(syz.0.135,6496,0):ocfs2_assign_bh:2416 ERROR: status = -30
(syz.0.135,6496,0):ocfs2_inode_lock_full_nested:2511 ERROR: status = -30
(syz.0.135,6496,1):ocfs2_shutdown_local_alloc:411 ERROR: status = -30
------------[ cut here ]------------
kernel BUG at fs/ocfs2/journal.c:1034!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 6496 Comm: syz.0.135 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
RIP: 0010:ocfs2_journal_toggle_dirty+0x338/0x340 fs/ocfs2/journal.c:1034
Code: fe ff ff e8 0a 59 1b 07 89 d9 80 e1 07 80 c1 03 38 c1 0f 8c 55 fe ff ff 48 89 df e8 b2 3a 89 fe e9 48 fe ff ff e8 d8 cc 31 fe <0f> 0b 66 0f 1f 44 00 00 f3 0f 1e fa 55 48 89 e5 41 57 41 56 41 55
RSP: 0018:ffffc9000b7a6f80 EFLAGS: 00010293
RAX: ffffffff8353c3e8 RBX: 00000000ffffffff RCX: ffff88802ac33c00
RDX: 0000000000000000 RSI: 00000000ffffffff RDI: 0000000000000000
RBP: ffffc9000b7a7030 R08: ffffffff90da960f R09: 1ffffffff21b52c1
R10: dffffc0000000000 R11: fffffbfff21b52c2 R12: 1ffff1100b5d237e
R13: ffff88805961c600 R14: ffff88801ebf3400 R15: ffff88805ae91bf0
FS: 00007ffa828c76c0(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f7da660b000 CR3: 000000002c45b000 CR4: 00000000003506e0
Call Trace:
<TASK>
ocfs2_journal_shutdown+0x525/0xaa0 fs/ocfs2/journal.c:1116
ocfs2_mount_volume+0x12e0/0x14d0 fs/ocfs2/super.c:1841
ocfs2_fill_super+0x3462/0x4d90 fs/ocfs2/super.c:1084
mount_bdev+0x22b/0x2d0 fs/super.c:1643
legacy_get_tree+0xea/0x180 fs/fs_context.c:662
vfs_get_tree+0x8c/0x280 fs/super.c:1764
do_new_mount+0x24b/0xa40 fs/namespace.c:3386
do_mount fs/namespace.c:3726 [inline]
__do_sys_mount fs/namespace.c:3935 [inline]
__se_sys_mount+0x2da/0x3c0 fs/namespace.c:3912
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7ffa81990eea
Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 de 1a 00 00 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffa828c6e68 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007ffa828c6ef0 RCX: 00007ffa81990eea
RDX: 0000200000004440 RSI: 0000200000000040 RDI: 00007ffa828c6eb0
RBP: 0000200000004440 R08: 00007ffa828c6ef0 R09: 00000000000008c0
R10: 00000000000008c0 R11: 0000000000000246 R12: 0000200000000040
R13: 00007ffa828c6eb0 R14: 0000000000004421 R15: 0000200000000080
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:ocfs2_journal_toggle_dirty+0x338/0x340 fs/ocfs2/journal.c:1034
Code: fe ff ff e8 0a 59 1b 07 89 d9 80 e1 07 80 c1 03 38 c1 0f 8c 55 fe ff ff 48 89 df e8 b2 3a 89 fe e9 48 fe ff ff e8 d8 cc 31 fe <0f> 0b 66 0f 1f 44 00 00 f3 0f 1e fa 55 48 89 e5 41 57 41 56 41 55
RSP: 0018:ffffc9000b7a6f80 EFLAGS: 00010293
RAX: ffffffff8353c3e8 RBX: 00000000ffffffff RCX: ffff88802ac33c00
RDX: 0000000000000000 RSI: 00000000ffffffff RDI: 0000000000000000
RBP: ffffc9000b7a7030 R08: ffffffff90da960f R09: 1ffffffff21b52c1
R10: dffffc0000000000 R11: fffffbfff21b52c2 R12: 1ffff1100b5d237e
R13: ffff88805961c600 R14: ffff88801ebf3400 R15: ffff88805ae91bf0
FS: 00007ffa828c76c0(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f7dae972a60 CR3: 000000002c45b000 CR4: 00000000003506f0


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