syzbot


upstream boot error: can't ssh into the instance (4)
Status: closed as invalid on 2020/02/07 07:17
Reported-by: syzbot+@syzkaller.appspotmail.com
First crash: 394d, last: 394d
similar bugs (8):
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream upstream boot error: can't ssh into the instance (5) 1 392d 392d 0/21 closed as invalid on 2020/02/09 07:17
upstream upstream boot error: can't ssh into the instance (2) 45 770d 770d 12/21 fixed on 2019/03/06 07:43
upstream upstream boot error: can't ssh into the instance (6) 1 391d 391d 0/21 closed as invalid on 2020/02/10 07:37
upstream upstream boot error: can't ssh into the instance (9) 3 38d 38d 0/21 closed as invalid on 2021/01/28 07:47
upstream upstream boot error: can't ssh into the instance 21 1025d 1064d 0/21 closed as invalid on 2018/06/14 06:16
upstream upstream boot error: can't ssh into the instance (8) 3 39d 39d 0/21 closed as invalid on 2021/01/27 17:06
upstream upstream boot error: can't ssh into the instance (3) 1 607d 607d 0/21 closed as invalid on 2019/07/14 14:27
upstream upstream boot error: can't ssh into the instance (7) 316 137d 379d 0/21 auto-closed as invalid on 2021/01/19 09:15
Crashes (1):
Manager Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Title
ci-upstream-kasan-gce-smack-root 2020/02/07 02:29 upstream 90568ecf 06150bf1 .config log