[v5.15] WARNING in start_this_handle

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 68efe5a6c16a Linux 5.15.197
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=173f099a580000
kernel config: https://syzkaller.appspot.com/x/.config?x=7e6ed99963d6ee1d
dashboard link: https://syzkaller.appspot.com/bug?extid=f9448b043adf45eb024b
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=12dee99a580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1497d922580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/900f9b9bd850/disk-68efe5a6.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/1e089a5019a6/vmlinux-68efe5a6.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b319f477b907/bzImage-68efe5a6.xz
mounted in repro #1: https://storage.googleapis.com/syzbot-assets/f55088cc8a2d/mount_0.gz
fsck result: OK (log: https://syzkaller.appspot.com/x/fsck.log?x=133f099a580000)
mounted in repro #2: https://storage.googleapis.com/syzbot-assets/3804bdd987d3/mount_5.gz

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

------------[ cut here ]------------
WARNING: CPU: 0 PID: 4299 at include/linux/jbd2.h:1727 jbd2_journal_has_csum_v2or3 include/linux/jbd2.h:1726 [inline]
WARNING: CPU: 0 PID: 4299 at include/linux/jbd2.h:1727 jbd2_descriptor_blocks_per_trans fs/jbd2/transaction.c:75 [inline]
WARNING: CPU: 0 PID: 4299 at include/linux/jbd2.h:1727 jbd2_get_transaction fs/jbd2/transaction.c:112 [inline]
WARNING: CPU: 0 PID: 4299 at include/linux/jbd2.h:1727 start_this_handle+0xe9c/0x15a0 fs/jbd2/transaction.c:412
Modules linked in:
CPU: 0 PID: 4299 Comm: syz-executor Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
RIP: 0010:jbd2_journal_has_csum_v2or3 include/linux/jbd2.h:1726 [inline]
RIP: 0010:jbd2_descriptor_blocks_per_trans fs/jbd2/transaction.c:75 [inline]
RIP: 0010:jbd2_get_transaction fs/jbd2/transaction.c:112 [inline]
RIP: 0010:start_this_handle+0xe9c/0x15a0 fs/jbd2/transaction.c:412
Code: a1 ff e9 3f f5 ff ff 44 89 f1 80 e1 07 80 c1 03 38 c1 0f 8c 7a f5 ff ff 4c 89 f7 e8 0e 63 a1 ff e9 6d f5 ff ff e8 74 fa 5c ff <0f> 0b e9 40 fc ff ff 89 d1 80 e1 07 80 c1 03 38 c1 0f 8c 8a f5 ff
RSP: 0018:ffffc900030ff760 EFLAGS: 00010293
RAX: ffffffff821ad19c RBX: ffff888076378780 RCX: ffff888018bad940
RDX: 0000000000000000 RSI: 0000000008000000 RDI: 0000000000000000
RBP: ffffc900030ff980 R08: dffffc0000000000 R09: ffffed100ec6f10a
R10: ffffed100ec6f10a R11: 1ffff1100ec6f109 R12: ffff88807ed1c000
R13: ffff88807ed1c980 R14: 0000000000000200 R15: dffffc0000000000
FS: 000055557192a500(0000) GS:ffff8880b9000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007efdb69d0000 CR3: 000000002bb49000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
jbd2__journal_start+0x2b7/0x5a0 fs/jbd2/transaction.c:521
jbd2_journal_start+0x26/0x30 fs/jbd2/transaction.c:560
ocfs2_start_trans+0x374/0x6c0 fs/ocfs2/journal.c:376
ocfs2_shutdown_local_alloc+0x1fd/0xa10 fs/ocfs2/localalloc.c:416
ocfs2_dismount_volume+0x1de/0x880 fs/ocfs2/super.c:1885
generic_shutdown_super+0x130/0x300 fs/super.c:475
kill_block_super+0x7c/0xe0 fs/super.c:1427
deactivate_locked_super+0x93/0xf0 fs/super.c:335
cleanup_mnt+0x418/0x4d0 fs/namespace.c:1148
task_work_run+0x125/0x1a0 kernel/task_work.c:188
tracehook_notify_resume include/linux/tracehook.h:189 [inline]
exit_to_user_mode_loop+0x10f/0x130 kernel/entry/common.c:181
exit_to_user_mode_prepare+0xee/0x180 kernel/entry/common.c:214
__syscall_exit_to_user_mode_work kernel/entry/common.c:296 [inline]
syscall_exit_to_user_mode+0x16/0x40 kernel/entry/common.c:307
do_syscall_64+0x58/0xa0 arch/x86/entry/common.c:86
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f6835a5da77
Code: a8 ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 0f 1f 44 00 00 31 f6 e9 09 00 00 00 66 0f 1f 84 00 00 00 00 00 b8 a6 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 01 c3 48 c7 c2 a8 ff ff ff f7 d8 64 89 02 b8
RSP: 002b:00007fff7fd31f98 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 00007f6835ae0d7d RCX: 00007f6835a5da77
RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007fff7fd32050
RBP: 00007fff7fd32050 R08: 0000000000000000 R09: 0000000000000000
R10: 00000000ffffffff R11: 0000000000000246 R12: 00007fff7fd330e0
R13: 00007f6835ae0d7d R14: 0000000000015757 R15: 00007fff7fd33120
</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