ci starts bisection 2023-06-28 11:48:57.356038273 +0000 UTC m=+7680.201142870
bisecting fixing commit since a5088ee7251e5106a4efa9588a73866eb4b4154e
building syzkaller on eab8f94940b33c0a2cbc7d8eb2219862b6864b19
ensuring issue is reproducible on original commit a5088ee7251e5106a4efa9588a73866eb4b4154e

testing commit a5088ee7251e5106a4efa9588a73866eb4b4154e gcc
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
kernel signature: 95ae82d8ea66753b650181c403a5ec4a8608c7a10f4af38a6bd7cdbad2df1ba6
run #0: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback
run #1: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback
run #2: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback
run #3: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback
run #4: crashed: WARNING: suspicious RCU usage in ntfs_fill_super
run #5: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback
run #6: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback
run #7: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback
run #8: crashed: invalid opcode in corrupted
run #9: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback
run #10: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback
run #11: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback
run #12: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback
run #13: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback
run #14: crashed: KASAN: wild-memory-access Read in inode_wait_for_writeback
run #15: crashed: WARNING: suspicious RCU usage in ntfs_fill_super
run #16: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback
run #17: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback
run #18: OK
run #19: OK
testing current HEAD 6aeadf7896bff4ca230702daba8788455e6b866e
testing commit 6aeadf7896bff4ca230702daba8788455e6b866e gcc
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
kernel signature: e1aac5493c18fa55f06a4c11e6363929711880bbcede61670059abdc64e6cad6
run #0: basic kernel testing failed: UBSAN: array-index-out-of-bounds in alloc_pid
run #1: basic kernel testing failed: UBSAN: array-index-out-of-bounds in alloc_pid
run #2: basic kernel testing failed: UBSAN: array-index-out-of-bounds in alloc_pid
run #3: basic kernel testing failed: UBSAN: array-index-out-of-bounds in alloc_pid
run #4: basic kernel testing failed: UBSAN: array-index-out-of-bounds in alloc_pid
run #5: basic kernel testing failed: UBSAN: array-index-out-of-bounds in alloc_pid
run #6: basic kernel testing failed: UBSAN: array-index-out-of-bounds in alloc_pid
run #7: basic kernel testing failed: UBSAN: array-index-out-of-bounds in alloc_pid
run #8: basic kernel testing failed: UBSAN: array-index-out-of-bounds in alloc_pid
run #9: basic kernel testing failed: timed out
HEAD had kernel build, boot or test errors
revisions tested: 2, total time: 35m39.929824405s (build: 18m18.947143638s, test: 16m2.997661048s)
crash still not fixed on HEAD or HEAD had kernel test errors
commit msg: Merge tag 'docs-arm64-move' of git://git.lwn.net/linux
crash: failed testing reproducer on 6aeadf7896bff4ca230702daba8788455e6b866e