kernel BUG in __ext4_journal_stop

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 4ec71a9ec769 ANDROID: cpu/hotplug: call perf event through..
git tree: android13-5.15-lts
console+strace: https://syzkaller.appspot.com/x/log.txt?x=16ba2a75880000
kernel config: https://syzkaller.appspot.com/x/.config?x=5f64a7340a9acccc
dashboard link: https://syzkaller.appspot.com/bug?extid=4aa1947d48b60f72a9af
compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13dfcf55880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16fa4d73880000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/93b972e96678/disk-4ec71a9e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/10d3ac64bada/vmlinux-4ec71a9e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/70ae0159c6d1/bzImage-4ec71a9e.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/a002f2289e55/mount_0.gz

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

EXT4-fs (loop0): mounted filesystem without journal. Opts: ,errors=continue. Quota mode: none.
------------[ cut here ]------------
kernel BUG at fs/ext4/ext4_jbd2.c:53!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 452 Comm: syz-executor270 Not tainted 5.15.74-syzkaller-00001-g4ec71a9ec769 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
RIP: 0010:ext4_put_nojournal fs/ext4/ext4_jbd2.c:53 [inline]
RIP: 0010:__ext4_journal_stop+0x1b3/0x1c0 fs/ext4/ext4_jbd2.c:116
Code: c3 89 f9 80 e1 07 80 c1 03 38 c1 0f 8c f8 fe ff ff e8 a1 3f cc ff 48 ba 00 00 00 00 00 fc ff df e9 e4 fe ff ff e8 fd f2 89 ff <0f> 0b 66 2e 0f 1f 84 00 00 00 00 00 90 55 48 89 e5 41 57 41 56 41
RSP: 0018:ffffc900009f76b8 EFLAGS: 00010293
RAX: ffffffff81e79e93 RBX: ffffffff8603902d RCX: ffff88810c3da780
RDX: 0000000000000000 RSI: 0000000000000331 RDI: ffffffff8603902d
RBP: ffffc900009f76f0 R08: ffffffff81ed2e18 R09: ffffed1023b9f661
R10: ffffed1023b9f661 R11: 1ffff11023b9f660 R12: ffff888109976ad8
R13: 0000000000000000 R14: 0000000000000012 R15: 0000000000000331
FS: 00007fe81c3e0700(0000) GS:ffff8881f7000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fe8140bf718 CR3: 000000010c0b4000 CR4: 00000000003506b0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
ext4_write_inline_data_end+0xa50/0xe10 fs/ext4/inline.c:817
ext4_da_write_end+0x3d7/0xa70 fs/ext4/inode.c:3076
generic_perform_write+0x3c7/0x5d0 mm/filemap.c:3836
ext4_buffered_write_iter+0x49b/0x630 fs/ext4/file.c:271
ext4_file_write_iter+0x456/0x1dc0
call_write_iter include/linux/fs.h:2129 [inline]
new_sync_write fs/read_write.c:507 [inline]
vfs_write+0xc8d/0x1050 fs/read_write.c:594
ksys_write+0x198/0x2c0 fs/read_write.c:647
__do_sys_write fs/read_write.c:659 [inline]
__se_sys_write fs/read_write.c:656 [inline]
__x64_sys_write+0x7b/0x90 fs/read_write.c:656
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x44/0xd0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7fe81c434579
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 71 15 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fe81c3e02f8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007fe81c4b97a0 RCX: 00007fe81c434579
RDX: 0000000000000009 RSI: 0000000020000f80 RDI: 0000000000000004
RBP: 00007fe81c486828 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007fe81c4860c0
R13: 0000000020000800 R14: 0030656c69662f2e R15: 00007fe81c4b97a8
</TASK>
Modules linked in:
---[ end trace a17cf528fe92cc36 ]---
RIP: 0010:ext4_put_nojournal fs/ext4/ext4_jbd2.c:53 [inline]
RIP: 0010:__ext4_journal_stop+0x1b3/0x1c0 fs/ext4/ext4_jbd2.c:116
Code: c3 89 f9 80 e1 07 80 c1 03 38 c1 0f 8c f8 fe ff ff e8 a1 3f cc ff 48 ba 00 00 00 00 00 fc ff df e9 e4 fe ff ff e8 fd f2 89 ff <0f> 0b 66 2e 0f 1f 84 00 00 00 00 00 90 55 48 89 e5 41 57 41 56 41
RSP: 0018:ffffc900009f76b8 EFLAGS: 00010293
RAX: ffffffff81e79e93 RBX: ffffffff8603902d RCX: ffff88810c3da780
RDX: 0000000000000000 RSI: 0000000000000331 RDI: ffffffff8603902d
RBP: ffffc900009f76f0 R08: ffffffff81ed2e18 R09: ffffed1023b9f661
R10: ffffed1023b9f661 R11: 1ffff11023b9f660 R12: ffff888109976ad8
R13: 0000000000000000 R14: 0000000000000012 R15: 0000000000000331
FS: 00007fe81c3e0700(0000) GS:ffff8881f7000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fe8140bf718 CR3: 000000010c0b4000 CR4: 00000000003506b0
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.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches