syzbot
Android 5.10
Android 5.15
Android 5.4
Android 6.1
Android 6.12
FreeBSD
Linux
Linux 5.15
Linux 6.1
Linux 6.6
NetBSD
OpenBSD
gVisor
sign-in
|
mailing list
|
source
|
docs
|
🏰
🐞 Open [1546]
≡
Subsystems
🐞 Fixed [7629]
🐞 Invalid [19970]
⬇
Missing Backports [217]
≡
Crashes
📈
Graphs
Kernel Health
Bugs/Month
Bug Lifetimes
Bug Resolution Rate
Fuzzing
📈
Coverage
Total
Repo Heatmap
Subsystems Heatmap
✨ AI
💬
Send us feedback
bpf-next boot error: can't ssh into the instance (4)
Status: closed as invalid on 2020/08/19 06:54
First crash: 2274d, last: 2274d
▶
▼
Similar bugs (3)
Kernel
Title
Rank
🛈
Repro
Cause bisect
Fix bisect
Count
Last
Reported
Patched
Status
upstream
bpf-next boot error: can't ssh into the instance
-1
1
3098d
3098d
0/29
closed as invalid on 2018/06/14 06:06
upstream
bpf-next boot error: can't ssh into the instance (3)
-1
3
2275d
2275d
0/29
closed as invalid on 2020/08/18 13:14
upstream
bpf-next boot error: can't ssh into the instance (2)
-1
1
2427d
2427d
0/29
closed as invalid on 2020/04/19 19:44
Crashes (3):
Time
Kernel
Commit
Syzkaller
Config
Log
Report
Syz repro
C repro
VM info
Assets
(
help?
)
Manager
Title
2020/08/19 00:35
bpf-next
65bb2e0fc5a6
6fe61c6b
.config
console log
ci-upstream-bpf-next-kasan-gce
2020/08/19 00:35
bpf-next
65bb2e0fc5a6
6fe61c6b
.config
console log
ci-upstream-bpf-next-kasan-gce
2020/08/19 00:35
bpf-next
65bb2e0fc5a6
6fe61c6b
.config
console log
ci-upstream-bpf-next-kasan-gce
*
Struck through
repros no longer work on HEAD.