syzbot

 sign-in | mailing list | source | docs
🐞 Open [978] ≡ Subsystems 🐞 Fixed [5235] 🐞 Invalid [12492] ⬇ Missing Backports [83] 📈 Kernel Health 📈 Bug Lifetimes 📈 Fuzzing 📈 Crashes 💬 Send us feedback

net-next boot error: can't ssh into the instance (3)

Status: auto-closed as invalid on 2020/09/25 01:22
Reported-by: syzbot+1312d700c503da6008a1@syzkaller.appspotmail.com
First crash: 1529d, last: 1426d
▶ ▼ Discussions (1)
Title Replies (including bot) Last reply
net-next boot error: can't ssh into the instance (3) 0 (1) 2020/02/19 10:27
▶ ▼ Similar bugs (5)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream net-next boot error: can't ssh into the instance (2) 2 1722d 1734d 0/26 auto-closed as invalid on 2019/11/04 04:41
upstream net-next boot error: can't ssh into the instance (6) 1 27d 27d 0/26 closed as invalid on 2024/03/27 09:32
upstream net-next boot error: can't ssh into the instance 33 1910d 1912d 11/26 fixed on 2019/03/06 07:43
upstream net-next boot error: can't ssh into the instance (5) 1 369d 369d 0/26 auto-obsoleted due to no activity on 2023/07/18 18:50
upstream net-next boot error: can't ssh into the instance (4) 3 1103d 1072d 0/26 closed as invalid on 2021/05/17 11:23
Crashes (2):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2020/05/28 01:21 net-next-old 50ce4c099beb 142a0957 .config console log ci-upstream-net-kasan-gce
2020/02/14 22:59 net-next-old 2019fc96af22 5d7b90f1 .config console log ci-upstream-net-kasan-gce
* Struck through repros no longer work on HEAD.