[v6.1] kernel BUG in __ext4_journal_stop

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 61fd484b2cf6 Linux 6.1.38
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17f4341aa80000
kernel config: https://syzkaller.appspot.com/x/.config?x=43a813745c91c8b3
dashboard link: https://syzkaller.appspot.com/bug?extid=178918fce2b18002808f
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1012e862a80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14b97596a80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/f3fe059efa91/disk-61fd484b.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/b69bfadef125/vmlinux-61fd484b.xz
kernel image: https://storage.googleapis.com/syzbot-assets/8ecbf54ec382/bzImage-61fd484b.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/73fa3dae1449/mount_0.gz

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

------------[ cut here ]------------
kernel BUG at fs/ext4/ext4_jbd2.c:53!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 4165 Comm: syz-executor247 Not tainted 6.1.38-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/03/2023
RIP: 0010:ext4_put_nojournal fs/ext4/ext4_jbd2.c:53 [inline]
RIP: 0010:__ext4_journal_stop+0x18b/0x190 fs/ext4/ext4_jbd2.c:116
Code: 5b 41 5c 41 5d 41 5e 41 5f 5d c3 89 f9 80 e1 07 80 c1 03 38 c1 0f 8c 11 ff ff ff e8 3f 29 b0 ff e9 07 ff ff ff e8 85 c3 59 ff <0f> 0b 0f 1f 00 55 41 57 41 56 41 55 41 54 53 48 83 ec 10 89 d5 89
RSP: 0018:ffffc9000495f200 EFLAGS: 00010293
RAX: ffffffff823017bb RBX: 0000000000000000 RCX: ffff8880206bbb80
RDX: 0000000000000000 RSI: 000000000000032c RDI: ffffffff8c7a3fb3
RBP: 000000000000032c R08: ffffffff8235ecd3 R09: fffffbfff1ca6a76
R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffff1100df9c7c8
R13: 0000000000000008 R14: 1ffff1100df9c7e6 R15: ffffffff8c7a3fb3
FS: 00007f7c4446c6c0(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fffbde21158 CR3: 0000000070ec5000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
ext4_write_inline_data_end+0xa6a/0x10c0 fs/ext4/inline.c:812
generic_perform_write+0x3e9/0x5e0 mm/filemap.c:3765
ext4_buffered_write_iter+0x122/0x3a0 fs/ext4/file.c:285
ext4_file_write_iter+0x1d2/0x18f0
do_iter_write+0x6e6/0xc50 fs/read_write.c:861
iter_file_splice_write+0x806/0xfa0 fs/splice.c:686
do_splice_from fs/splice.c:764 [inline]
direct_splice_actor+0xe3/0x1c0 fs/splice.c:931
splice_direct_to_actor+0x4c0/0xbd0 fs/splice.c:886
do_splice_direct+0x27f/0x3c0 fs/splice.c:974
do_sendfile+0x61c/0xff0 fs/read_write.c:1255
__do_sys_sendfile64 fs/read_write.c:1323 [inline]
__se_sys_sendfile64+0x178/0x1e0 fs/read_write.c:1309
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f7c4c7d1aa9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 61 1a 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f7c4446c218 EFLAGS: 00000246 ORIG_RAX: 0000000000000028
RAX: ffffffffffffffda RBX: 00007f7c4c8596f8 RCX: 00007f7c4c7d1aa9
RDX: 0000000000000000 RSI: 0000000000000005 RDI: 0000000000000004
RBP: 00007f7c4c8596f0 R08: 00007fffbde21177 R09: 0000000000000000
R10: 0000000000000004 R11: 0000000000000246 R12: 00007f7c4c825840
R13: 00007f7c4c8250c0 R14: 0000000020000f40 R15: 0030656c69662f2e
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:ext4_put_nojournal fs/ext4/ext4_jbd2.c:53 [inline]
RIP: 0010:__ext4_journal_stop+0x18b/0x190 fs/ext4/ext4_jbd2.c:116
Code: 5b 41 5c 41 5d 41 5e 41 5f 5d c3 89 f9 80 e1 07 80 c1 03 38 c1 0f 8c 11 ff ff ff e8 3f 29 b0 ff e9 07 ff ff ff e8 85 c3 59 ff <0f> 0b 0f 1f 00 55 41 57 41 56 41 55 41 54 53 48 83 ec 10 89 d5 89
RSP: 0018:ffffc9000495f200 EFLAGS: 00010293
RAX: ffffffff823017bb RBX: 0000000000000000 RCX: ffff8880206bbb80
RDX: 0000000000000000 RSI: 000000000000032c RDI: ffffffff8c7a3fb3
RBP: 000000000000032c R08: ffffffff8235ecd3 R09: fffffbfff1ca6a76
R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffff1100df9c7c8
R13: 0000000000000008 R14: 1ffff1100df9c7e6 R15: ffffffff8c7a3fb3
FS: 00007f7c4446c6c0(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f7c4446c000 CR3: 0000000070ec5000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


---
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 bug is already fixed, 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 change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup