[v5.15] kernel BUG in flush_commit_list

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 284087d4f7d5 Linux 5.15.158
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=102ead1f180000
kernel config: https://syzkaller.appspot.com/x/.config?x=b0dd54e4b5171ebc
dashboard link: https://syzkaller.appspot.com/bug?extid=d3bb533cf8d65d1665f1
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/c2e33c1db6bf/disk-284087d4.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/d9f77284af1d/vmlinux-284087d4.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a600323dd149/bzImage-284087d4.xz

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

------------[ cut here ]------------
kernel BUG at fs/reiserfs/journal.c:1105!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 3677 Comm: syz-executor.2 Not tainted 5.15.158-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
RIP: 0010:flush_commit_list+0x1e91/0x1ec0 fs/reiserfs/journal.c:1105
Code: 0b 08 e8 f2 a3 6d ff 0f 0b e8 eb a3 6d ff 0f 0b e8 e4 a3 6d ff 0f 0b e8 dd a3 6d ff 0f 0b e8 d6 a3 6d ff 0f 0b e8 cf a3 6d ff <0f> 0b e8 c8 a3 6d ff 0f 0b 48 8b 4c 24 20 80 e1 07 80 c1 03 38 c1
RSP: 0018:ffffc900044371a0 EFLAGS: 00010246
RAX: ffffffff8212b8f1 RBX: 0000000000000002 RCX: 0000000000040000
RDX: ffffc9000368b000 RSI: 000000000003ffff RDI: 0000000000040000
RBP: ffffc90004437308 R08: ffffffff8212adea R09: ffffed100e9c96e9
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff888141fb0678
R13: ffff888141fb0000 R14: ffff88805fe5b4d0 R15: 1ffff1100bfcb69a
FS: 00007f415d9336c0(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000c000c634ac CR3: 0000000075f7d000 CR4: 00000000003506f0
DR0: 0000000000002800 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
flush_journal_list+0x2a8/0x1c80 fs/reiserfs/journal.c:1388
flush_used_journal_lists+0x1254/0x15d0 fs/reiserfs/journal.c:1826
do_journal_end+0x391a/0x4650
do_journal_begin_r+0x950/0x1000
journal_begin+0x148/0x350 fs/reiserfs/journal.c:3253
reiserfs_fill_super+0x1812/0x2690 fs/reiserfs/super.c:2108
mount_bdev+0x2c9/0x3f0 fs/super.c:1387
legacy_get_tree+0xeb/0x180 fs/fs_context.c:611
vfs_get_tree+0x88/0x270 fs/super.c:1517
do_new_mount+0x2ba/0xb40 fs/namespace.c:3005
do_mount fs/namespace.c:3348 [inline]
__do_sys_mount fs/namespace.c:3556 [inline]
__se_sys_mount+0x2d5/0x3c0 fs/namespace.c:3533
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f415f3c23aa
Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 de 09 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 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f415d932ef8 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f415d932f80 RCX: 00007f415f3c23aa
RDX: 0000000020000040 RSI: 0000000020000280 RDI: 00007f415d932f40
RBP: 0000000020000040 R08: 00007f415d932f80 R09: 0000000001000098
R10: 0000000001000098 R11: 0000000000000202 R12: 0000000020000280
R13: 00007f415d932f40 R14: 00000000000010fd R15: 0000000020000300
</TASK>
Modules linked in:
---[ end trace 563896875931a268 ]---
RIP: 0010:flush_commit_list+0x1e91/0x1ec0 fs/reiserfs/journal.c:1105
Code: 0b 08 e8 f2 a3 6d ff 0f 0b e8 eb a3 6d ff 0f 0b e8 e4 a3 6d ff 0f 0b e8 dd a3 6d ff 0f 0b e8 d6 a3 6d ff 0f 0b e8 cf a3 6d ff <0f> 0b e8 c8 a3 6d ff 0f 0b 48 8b 4c 24 20 80 e1 07 80 c1 03 38 c1
RSP: 0018:ffffc900044371a0 EFLAGS: 00010246
RAX: ffffffff8212b8f1 RBX: 0000000000000002 RCX: 0000000000040000
RDX: ffffc9000368b000 RSI: 000000000003ffff RDI: 0000000000040000
RBP: ffffc90004437308 R08: ffffffff8212adea R09: ffffed100e9c96e9
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff888141fb0678
R13: ffff888141fb0000 R14: ffff88805fe5b4d0 R15: 1ffff1100bfcb69a
FS: 00007f415d9336c0(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f3644f99000 CR3: 0000000075f7d000 CR4: 00000000003526e0
DR0: 0000000000002800 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 report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

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