ci2 starts bisection 2022-11-07 13:46:46.674037138 +0000 UTC m=+5409.486303748
bisecting fixing commit since b357fd1c2afc1a3e1b73dc4574bb7ac0e3bd4193
building syzkaller on feb5635181eb12a6e3516172a3f5af06a3bc93e1
ensuring issue is reproducible on original commit b357fd1c2afc1a3e1b73dc4574bb7ac0e3bd4193

testing commit b357fd1c2afc1a3e1b73dc4574bb7ac0e3bd4193 gcc
compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
kernel signature: b0ab527d6f3d18eb6370f2fa5ce6f963069096c4bc67b012200b9de7ca6c5e15
all runs: crashed: UBSAN: shift-out-of-bounds in dbSplit
testing current HEAD f0c4d9fc9cc9462659728d168387191387e903cc
testing commit f0c4d9fc9cc9462659728d168387191387e903cc gcc
compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
kernel signature: 58f3605c9e351918d3743182daad1e6d680c81396c06137d3fd0a1c8897df6e9
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: shift-out-of-bounds in dbSplit
run #2: crashed: UBSAN: shift-out-of-bounds in dbSplit
run #3: crashed: UBSAN: shift-out-of-bounds in dbSplit
run #4: crashed: UBSAN: shift-out-of-bounds in dbSplit
run #5: crashed: UBSAN: shift-out-of-bounds in dbSplit
run #6: crashed: UBSAN: shift-out-of-bounds in dbSplit
run #7: crashed: UBSAN: shift-out-of-bounds in dbSplit
run #8: crashed: UBSAN: shift-out-of-bounds in dbSplit
run #9: crashed: UBSAN: shift-out-of-bounds in dbSplit
revisions tested: 2, total time: 34m47.450325503s (build: 27m29.523591838s, test: 6m42.038968913s)
the crash still happens on HEAD
commit msg: Linux 6.1-rc4
crash: UBSAN: shift-out-of-bounds in dbSplit
loop0: detected capacity change from 0 to 32768
================================================================================
UBSAN: shift-out-of-bounds in fs/jfs/jfs_dmap.c:2606:11
shift exponent 109 is too large for 32-bit type 'int'
CPU: 1 PID: 4164 Comm: syz-executor.0 Not tainted 6.1.0-rc4-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x12a/0x1be lib/dump_stack.c:106
 ubsan_epilogue lib/ubsan.c:151 [inline]
 __ubsan_handle_shift_out_of_bounds+0x222/0x260 lib/ubsan.c:322
 dbSplit+0x15e/0x170 fs/jfs/jfs_dmap.c:2606
 dbAllocBits+0x9f/0x850 fs/jfs/jfs_dmap.c:2158
 dbAllocDmap fs/jfs/jfs_dmap.c:1999 [inline]
 dbAllocNear+0x1ff/0x330 fs/jfs/jfs_dmap.c:1228
 dbAlloc+0x5fa/0xa30 fs/jfs/jfs_dmap.c:813
 diNewExt+0x850/0x3890 fs/jfs/jfs_imap.c:2251
 diAllocExt fs/jfs/jfs_imap.c:1945 [inline]
 diAllocAG+0xb02/0x1f00 fs/jfs/jfs_imap.c:1662
 diAlloc+0x3af/0x1280 fs/jfs/jfs_imap.c:1583
 ialloc+0x74/0x990 fs/jfs/jfs_inode.c:56
 jfs_mkdir+0xf4/0x950 fs/jfs/namei.c:225
 vfs_mkdir+0x2d3/0x460 fs/namei.c:4035
 do_mkdirat+0x229/0x490 fs/namei.c:4060
 __do_sys_mkdir fs/namei.c:4080 [inline]
 __se_sys_mkdir fs/namei.c:4078 [inline]
 __x64_sys_mkdir+0x65/0x70 fs/namei.c:4078
 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:0x7f873648a5a9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 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:00007f8737690168 EFLAGS: 00000246 ORIG_RAX: 0000000000000053
RAX: ffffffffffffffda RBX: 00007f87365abf80 RCX: 00007f873648a5a9
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 00000000200052c0
RBP: 00007f87364e5580 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffed13c48cf R14: 00007f8737690300 R15: 0000000000022000
 </TASK>
================================================================================