syzbot

 sign-in | mailing list | source | docs
🐞 Open [963] 🐞 Fixed [3805] 🐞 Invalid [8174] 📈 Kernel Health 📈 Bug Lifetimes 📈 Fuzzing 📈 Crashes

linux-next boot error: can't ssh into the instance
Status: closed as invalid on 2018/02/14 13:58
Reported-by: syzbot+@syzkaller.appspotmail.com
First crash: 1617d, last: 1610d
similar bugs (4):
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream linux-next boot error: can't ssh into the instance (2) 6 1206d 1206d 0/22 closed as invalid on 2019/06/11 06:33
upstream linux-next boot error: can't ssh into the instance (5) 15 89d 90d 0/22 auto-closed as invalid on 2022/04/06 18:40
upstream linux-next boot error: can't ssh into the instance (3) 6 918d 919d 0/22 closed as invalid on 2019/11/19 17:42
upstream linux-next boot error: can't ssh into the instance (4) 9 401d 373d 0/22 closed as invalid on 2021/05/17 11:46
Crashes (2):
Manager Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Title
ci-upstream-next-kasan-gce 2017/12/27 20:54 linux-next 3514267557aa 7d240098 .config log
ci-upstream-next-kasan-gce 2017/12/20 05:22 linux-next 7dc9f647127d 2d836b1d .config log