[v6.1] UBSAN: array-index-out-of-bounds in txCommit

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 0f4ac6b4c5f0 Linux 6.1.37
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=111c3c02a80000
kernel config: https://syzkaller.appspot.com/x/.config?x=b38e28d864b6a1fc
dashboard link: https://syzkaller.appspot.com/bug?extid=07bc361486c2f9420c7a
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/b81b32428cff/disk-0f4ac6b4.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/98c79ff1a964/vmlinux-0f4ac6b4.xz
kernel image: https://storage.googleapis.com/syzbot-assets/184fb0dfef6d/bzImage-0f4ac6b4.xz

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

UBSAN: array-index-out-of-bounds in fs/jfs/jfs_txnmgr.c:1738:5
index 18 is out of range for type 'xad_t[18]' (aka 'struct xad[18]')
CPU: 0 PID: 10873 Comm: syz-executor.5 Not tainted 6.1.37-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/27/2023
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
ubsan_epilogue lib/ubsan.c:151 [inline]
__ubsan_handle_out_of_bounds+0x118/0x140 lib/ubsan.c:282
xtLog fs/jfs/jfs_txnmgr.c:1738 [inline]
txLog fs/jfs/jfs_txnmgr.c:1391 [inline]
txCommit+0x3f07/0x6ba0 fs/jfs/jfs_txnmgr.c:1259
jfs_commit_inode+0x362/0x580 fs/jfs/inode.c:108
extAlloc+0xc94/0x1010 fs/jfs/jfs_extent.c:172
jfs_get_block+0x417/0xe50 fs/jfs/inode.c:248
get_more_blocks fs/direct-io.c:665 [inline]
do_direct_IO fs/direct-io.c:953 [inline]
__blockdev_direct_IO+0x1ba3/0x4340 fs/direct-io.c:1266
blockdev_direct_IO include/linux/fs.h:3228 [inline]
jfs_direct_IO+0xf6/0x1e0 fs/jfs/inode.c:336
generic_file_direct_write+0x204/0x460 mm/filemap.c:3678
__generic_file_write_iter+0x1c4/0x400 mm/filemap.c:3838
generic_file_write_iter+0xab/0x310 mm/filemap.c:3914
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:0x7fc7e188c389
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 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:00007fc7d8fdd168 EFLAGS: 00000246 ORIG_RAX: 0000000000000028
RAX: ffffffffffffffda RBX: 00007fc7e19ac050 RCX: 00007fc7e188c389
RDX: 0000000000000000 RSI: 0000000000000005 RDI: 0000000000000004
RBP: 00007fc7e18d7493 R08: 0000000000000000 R09: 0000000000000000
R10: 0001000000201004 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffdedf7592f R14: 00007fc7d8fdd300 R15: 0000000000022000
</TASK>
================================================================================


---
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 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

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.