syzbot

 sign-in | mailing list | source | docs
🐞 Open [1033] 🐞 Fixed [3377] 🐞 Invalid [6486]

bpf-next boot error: can't ssh into the instance (4)
Status: closed as invalid on 2020/08/19 06:54
Reported-by: syzbot+@syzkaller.appspotmail.com
First crash: 397d, last: 397d
similar bugs (3):
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream bpf-next boot error: can't ssh into the instance 1 1222d 1222d 0/22 closed as invalid on 2018/06/14 06:06
upstream bpf-next boot error: can't ssh into the instance (3) 3 398d 398d 0/22 closed as invalid on 2020/08/18 13:14
upstream bpf-next boot error: can't ssh into the instance (2) 1 550d 550d 0/22 closed as invalid on 2020/04/19 19:44
Crashes (3):
Manager Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Title
ci-upstream-bpf-next-kasan-gce 2020/08/19 00:35 bpf-next 65bb2e0fc5a6 6fe61c6b .config log
ci-upstream-bpf-next-kasan-gce 2020/08/19 00:35 bpf-next 65bb2e0fc5a6 6fe61c6b .config log
ci-upstream-bpf-next-kasan-gce 2020/08/19 00:35 bpf-next 65bb2e0fc5a6 6fe61c6b .config log