[v5.15] kernel BUG in flush_journal_list

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: d54cfc420586 Linux 5.15.120
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=105b861aa80000
kernel config: https://syzkaller.appspot.com/x/.config?x=f546a5c7ff981a94
dashboard link: https://syzkaller.appspot.com/bug?extid=b7282a2fdc517e2c9940
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=104139e4a80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16c44396a80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/601dfce79849/disk-d54cfc42.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/b8e802138c25/vmlinux-d54cfc42.xz
kernel image: https://storage.googleapis.com/syzbot-assets/9b3b48ff5c05/bzImage-d54cfc42.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/89de2ce0cf16/mount_0.gz

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

REISERFS error (device loop0): vs-13050 reiserfs_update_sd_size: i/o failure occurred trying to update [2 2 0x0 SD] stat data
REISERFS warning (device loop0): clm-6006 reiserfs_dirty_inode: writing inode 2 on readonly FS
------------[ cut here ]------------
kernel BUG at fs/reiserfs/journal.c:1449!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 3500 Comm: syz-executor409 Not tainted 5.15.120-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/03/2023
RIP: 0010:flush_journal_list+0x1c41/0x1c80 fs/reiserfs/journal.c:1449
Code: eb 8d 16 8c 48 c7 c1 80 73 9b 8a e8 89 60 fb ff e8 84 51 6e ff 0f 0b e8 7d 51 6e ff 0f 0b e8 76 51 6e ff 0f 0b e8 6f 51 6e ff <0f> 0b e8 68 51 6e ff 0f 0b e8 61 51 6e ff 0f 0b e8 5a 51 6e ff 0f
RSP: 0018:ffffc900024df6e0 EFLAGS: 00010293
RAX: ffffffff8211af31 RBX: 0000000000000001 RCX: ffff8880232e3b80
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000
RBP: 0000000000000000 R08: ffffffff821199b5 R09: ffffed100e7fb858
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff888073fdc2b8
R13: ffffc90002df30d8 R14: 1ffff1100e7fb857 R15: 1ffff920005be61d
FS: 0000000000000000(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f8b7e1ef1f8 CR3: 000000000c68e000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
flush_older_journal_lists fs/reiserfs/journal.c:1315 [inline]
flush_journal_list+0xeb5/0x1c80 fs/reiserfs/journal.c:1572
do_journal_end+0x32db/0x4650 fs/reiserfs/journal.c:4299
do_journal_release+0x478/0x4d0 fs/reiserfs/journal.c:1937
journal_release+0x1b/0x30 fs/reiserfs/journal.c:1968
reiserfs_put_super+0x237/0x4b0 fs/reiserfs/super.c:616
generic_shutdown_super+0x136/0x2c0 fs/super.c:475
kill_block_super+0x7a/0xe0 fs/super.c:1405
deactivate_locked_super+0xa0/0x110 fs/super.c:335
cleanup_mnt+0x44e/0x500 fs/namespace.c:1143
task_work_run+0x129/0x1a0 kernel/task_work.c:164
exit_task_work include/linux/task_work.h:32 [inline]
do_exit+0x6a3/0x2480 kernel/exit.c:872
do_group_exit+0x144/0x310 kernel/exit.c:994
__do_sys_exit_group kernel/exit.c:1005 [inline]
__se_sys_exit_group kernel/exit.c:1003 [inline]
__x64_sys_exit_group+0x3b/0x40 kernel/exit.c:1003
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+0x61/0xcb
RIP: 0033:0x7f8b7e1a4c89
Code: Unable to access opcode bytes at RIP 0x7f8b7e1a4c5f.
RSP: 002b:00007ffd938c5e18 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 00007f8b7e1a4c89
RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000001
RBP: 00007f8b7e222390 R08: ffffffffffffffb8 R09: 00007ffd938c5ef0
R10: 0000000020000000 R11: 0000000000000246 R12: 00007f8b7e222390
R13: 0000000000000000 R14: 00007f8b7e223100 R15: 00007f8b7e172f60
</TASK>
Modules linked in:
---[ end trace 52ed6d65f5bf5b0a ]---
RIP: 0010:flush_journal_list+0x1c41/0x1c80 fs/reiserfs/journal.c:1449
Code: eb 8d 16 8c 48 c7 c1 80 73 9b 8a e8 89 60 fb ff e8 84 51 6e ff 0f 0b e8 7d 51 6e ff 0f 0b e8 76 51 6e ff 0f 0b e8 6f 51 6e ff <0f> 0b e8 68 51 6e ff 0f 0b e8 61 51 6e ff 0f 0b e8 5a 51 6e ff 0f
RSP: 0018:ffffc900024df6e0 EFLAGS: 00010293
RAX: ffffffff8211af31 RBX: 0000000000000001 RCX: ffff8880232e3b80
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000
RBP: 0000000000000000 R08: ffffffff821199b5 R09: ffffed100e7fb858
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff888073fdc2b8
R13: ffffc90002df30d8 R14: 1ffff1100e7fb857 R15: 1ffff920005be61d
FS: 0000000000000000(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f8b7e1ef1f8 CR3: 000000000c68e000 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