[v5.15] UBSAN: array-index-out-of-bounds in diFree

Hello,

syzbot found the following issue on:

HEAD commit: 4878aadf2d15 Linux 5.15.161
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=140ee7a6980000
kernel config: https://syzkaller.appspot.com/x/.config?x=875d98826c53bf16
dashboard link: https://syzkaller.appspot.com/bug?extid=e70704cadcde378004b8
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/f227a150ea92/disk-4878aadf.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/6cfc50bf8b4e/vmlinux-4878aadf.xz
kernel image: https://storage.googleapis.com/syzbot-assets/23f7adc3c761/bzImage-4878aadf.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: [email protected]

================================================================================
UBSAN: array-index-out-of-bounds in fs/jfs/jfs_imap.c:886:2
index -134217728 is out of range for type 'struct mutex[128]'
CPU: 1 PID: 275 Comm: jfsCommit Not tainted 5.15.161-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/07/2024
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2d0 lib/dump_stack.c:106
ubsan_epilogue lib/ubsan.c:151 [inline]
__ubsan_handle_out_of_bounds+0x118/0x140 lib/ubsan.c:282
diFree+0x21bb/0x2fb0 fs/jfs/jfs_imap.c:886
jfs_evict_inode+0x329/0x440 fs/jfs/inode.c:156
evict+0x2a4/0x620 fs/inode.c:587
txUpdateMap+0x825/0x9e0 fs/jfs/jfs_txnmgr.c:2401
txLazyCommit fs/jfs/jfs_txnmgr.c:2698 [inline]
jfs_lazycommit+0x470/0xc30 fs/jfs/jfs_txnmgr.c:2766
kthread+0x3f6/0x4f0 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:300
</TASK>
================================================================================
Kernel panic - not syncing: UBSAN: panic_on_warn set ...
CPU: 0 PID: 275 Comm: jfsCommit Not tainted 5.15.161-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/07/2024
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2d0 lib/dump_stack.c:106
panic+0x318/0x860 kernel/panic.c:309
check_panic_on_warn+0x7e/0xa0 kernel/panic.c:229
ubsan_epilogue lib/ubsan.c:157 [inline]
__ubsan_handle_out_of_bounds+0x138/0x140 lib/ubsan.c:282
diFree+0x21bb/0x2fb0 fs/jfs/jfs_imap.c:886
jfs_evict_inode+0x329/0x440 fs/jfs/inode.c:156
evict+0x2a4/0x620 fs/inode.c:587
txUpdateMap+0x825/0x9e0 fs/jfs/jfs_txnmgr.c:2401
txLazyCommit fs/jfs/jfs_txnmgr.c:2698 [inline]
jfs_lazycommit+0x470/0xc30 fs/jfs/jfs_txnmgr.c:2766
kthread+0x3f6/0x4f0 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:300
</TASK>
Kernel Offset: disabled
Rebooting in 86400 seconds..


---
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 [email protected].

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

syzbot has found a reproducer for the following issue on:
console output: https://syzkaller.appspot.com/x/log.txt?x=10ce81c1980000
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14c6e41a980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14ed4c81980000
mounted in repro: https://storage.googleapis.com/syzbot-assets/0088c0ded5ea/mount_0.gz
CPU: 0 PID: 276 Comm: jfsCommit Not tainted 5.15.161-syzkaller #0
CPU: 0 PID: 276 Comm: jfsCommit Not tainted 5.15.161-syzkaller #0
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.

syzbot suspects this issue was fixed by commit:

commit 63f7fdf733add82f126ea00e2e48f6eba15ac4b9
Author: Jeongjun Park <[email protected]>
Date: Thu May 30 13:28:09 2024 +0000

jfs: Fix array-index-out-of-bounds in diFree

bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12861e77980000
start commit: 4878aadf2d15 Linux 5.15.161
git tree: linux-5.15.y
If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: jfs: Fix array-index-out-of-bounds in diFree

For information about bisection process see: https://goo.gl/tpsmEJ#bisection