ci2 starts bisection 2023-01-23 11:44:22.620025833 +0000 UTC m=+1300.237153887
bisecting fixing commit since b208b9fbbcba743fb269d15cb46a4036b01936b1
building syzkaller on 6d752409f178135881da3510c910bb11ae1f1381
ensuring issue is reproducible on original commit b208b9fbbcba743fb269d15cb46a4036b01936b1

testing commit b208b9fbbcba743fb269d15cb46a4036b01936b1 gcc
compiler: Debian clang version 13.0.1-6~deb11u1, GNU ld (GNU Binutils for Debian) 2.35.2
kernel signature: 3815392ca4d3b97f452e7a6dcba2ff1edc9f9b79a211c99c9e9d88adbe439053
all runs: crashed: UBSAN: array-index-out-of-bounds in dbJoin
testing current HEAD 2475bf0250dee99b477e0c56d7dc9d7ac3f04117
testing commit 2475bf0250dee99b477e0c56d7dc9d7ac3f04117 gcc
compiler: Debian clang version 13.0.1-6~deb11u1, GNU ld (GNU Binutils for Debian) 2.35.2
kernel signature: 32b961b6f4dc40e744d8d3378d834158e5d2d7c1e20449c4469e42230724e3e2
run #0: basic kernel testing failed: BUG: program execution failed: executor NUM: failed to write control pipe: write |NUM: broken pipe
run #1: crashed: UBSAN: array-index-out-of-bounds in dbJoin
run #2: crashed: UBSAN: array-index-out-of-bounds in dbJoin
run #3: crashed: UBSAN: array-index-out-of-bounds in dbJoin
run #4: crashed: UBSAN: array-index-out-of-bounds in dbJoin
run #5: crashed: UBSAN: array-index-out-of-bounds in dbJoin
run #6: crashed: UBSAN: array-index-out-of-bounds in dbJoin
run #7: crashed: UBSAN: array-index-out-of-bounds in dbJoin
run #8: crashed: UBSAN: array-index-out-of-bounds in dbJoin
run #9: crashed: UBSAN: array-index-out-of-bounds in dbJoin
revisions tested: 2, total time: 42m1.584128321s (build: 33m32.523062892s, test: 6m46.983334048s)
the crash still happens on HEAD
commit msg: Merge tag 'sched_urgent_for_v6.2_rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
crash: UBSAN: array-index-out-of-bounds in dbJoin
================================================================================
UBSAN: array-index-out-of-bounds in fs/jfs/jfs_dmap.c:2760:24
index 1426063360 is out of range for type 's8 [1365]'
CPU: 1 PID: 103 Comm: jfsCommit Not tainted 6.2.0-rc5-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/12/2023
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x12a/0x1c0 lib/dump_stack.c:106
 ubsan_epilogue lib/ubsan.c:151 [inline]
 __ubsan_handle_out_of_bounds+0xaf/0xe0 lib/ubsan.c:282
 dbJoin+0x227/0x260 fs/jfs/jfs_dmap.c:2760
 dbFreeBits+0x81/0xad0 fs/jfs/jfs_dmap.c:2320
 dbFreeDmap fs/jfs/jfs_dmap.c:2069 [inline]
 dbFree+0x2e5/0x550 fs/jfs/jfs_dmap.c:394
 txFreeMap+0x88f/0xcc0 fs/jfs/jfs_txnmgr.c:2510
 xtTruncate+0xc4f/0x3230 fs/jfs/jfs_xtree.c:2467
 jfs_free_zero_link+0x36f/0x650 fs/jfs/namei.c:758
 jfs_evict_inode+0x26d/0x370 fs/jfs/inode.c:153
 evict+0x262/0x550 fs/inode.c:664
 txUpdateMap+0x6c5/0x990 fs/jfs/jfs_txnmgr.c:2362
 txLazyCommit fs/jfs/jfs_txnmgr.c:2659 [inline]
 jfs_lazycommit+0x441/0xa20 fs/jfs/jfs_txnmgr.c:2727
 kthread+0x228/0x2a0 kernel/kthread.c:376
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
 </TASK>
================================================================================