ci starts bisection 2023-05-09 07:41:30.339988302 +0000 UTC m=+27290.212885301
bisecting fixing commit since 180eca540ae06246d594bdd8d8213426a259cc8c
building syzkaller on 098b5d530648147c744a7c2eb8b78c1307f9d3ce
ensuring issue is reproducible on original commit 180eca540ae06246d594bdd8d8213426a259cc8c

testing commit 180eca540ae06246d594bdd8d8213426a259cc8c gcc
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
kernel signature: 206da51865a31263f5697971cace77bc88dc99bbb1e7db270ed736b5ab925566
all runs: crashed: SYZFAIL: tun read failed
testing current HEAD ba0ad6ed89fd5dada3b7b65ef2b08e95d449d4ab
testing commit ba0ad6ed89fd5dada3b7b65ef2b08e95d449d4ab gcc
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
kernel signature: 0cd60bf8905090111fde04a530717af18ac7ec153d08c9082decab6281680bdf
run #0: crashed: SYZFAIL: tun read failed
run #1: crashed: SYZFAIL: tun read failed
run #2: crashed: SYZFAIL: tun read failed
run #3: crashed: SYZFAIL: wrong response packet
run #4: crashed: SYZFAIL: tun read failed
run #5: crashed: SYZFAIL: tun read failed
run #6: crashed: SYZFAIL: wrong response packet
run #7: crashed: SYZFAIL: tun read failed
run #8: crashed: SYZFAIL: wrong response packet
run #9: crashed: SYZFAIL: wrong response packet
crash still not fixed/happens on the oldest tested release
revisions tested: 2, total time: 24m5.190085798s (build: 14m56.797621021s, test: 8m5.09291799s)
crash still not fixed on HEAD or HEAD had kernel test errors
commit msg: media: nxp: imx8-isi: fix buiding on 32-bit
crash: SYZFAIL: wrong response packet
2023/05/09 08:05:34 executor failed 11 times: executor 0: exit status 67
SYZFAIL: wrong response packet
 (errno 16: Device or resource busy)
loop exited with status 67

SYZFAIL: wrong response packet
 (errno 16: Device or resource busy)
loop exited with status 67