syzbot


linux-next test error: BUG: program execution failed: executor NUM: exit status NUM

Status: auto-closed as invalid on 2022/06/06 07:20
Reported-by: syzbot+@syzkaller.appspotmail.com
First crash: 326d, last: 239d
similar bugs (2):
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream linux-next test error: BUG: program execution failed: executor NUM: exit status NUM (3) 4 72d 98d 0/24 auto-obsoleted due to no activity on 2022/11/20 09:57
upstream linux-next test error: BUG: program execution failed: executor NUM: exit status NUM (2) 1 116d 116d 0/24 closed as invalid on 2022/08/09 09:59

Sample crash report:
2022/04/07 07:16:38 testing simple program...
executing program
2022/04/07 07:16:42 BUG: program execution failed: 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

Crashes (3):
Manager Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Title
ci-upstream-linux-next-kasan-gce-root 2022/04/07 07:16 linux-next 2e9a9857569e 97582466 .config log report linux-next test error: BUG: program execution failed: executor NUM: exit status NUM
ci-upstream-linux-next-kasan-gce-root 2022/02/16 08:56 linux-next 763a906a02e9 8b9ca619 .config log report linux-next test error: BUG: program execution failed: executor NUM: exit status NUM
ci-upstream-linux-next-kasan-gce-root 2022/01/10 08:56 linux-next 57c149e506d5 2ca0d385 .config log report linux-next test error: BUG: program execution failed: executor NUM: exit status NUM
* Struck through repros no longer work on HEAD.