syzbot

 sign-in | mailing list | source | docs
🐞 Open [1273] ≡ Subsystems 🐞 Fixed [5370] 🐞 Invalid [12799] ⬇ Missing Backports [104] 📈 Kernel Health 📈 Bugs/Month 📈 Bug Lifetimes 📈 Fuzzing 📈 Crashes 💬 Send us feedback

bpf test error: SYZFATAL: failed to connect to host: dial tcp IP:NUM: connect: connection refused

Status: closed as invalid on 2024/05/25 16:55
First crash: 24d, last: 22d

Sample crash report:
Warning: Permanently added '10.128.0.155' (ED25519) to the list of known hosts.
2024/05/24 15:55:52 fuzzer started
2024/05/24 15:55:52 dialing manager at 10.128.0.169:30013
2024/05/24 15:55:52 SYZFATAL: failed to connect to host: dial tcp 10.128.0.169:30013: connect: connection refused

Crashes (3):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/05/24 16:10 bpf 44382b3ed6b2 8f98448e .config console log report [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce bpf test error: SYZFATAL: failed to connect to host: dial tcp IP:NUM: connect: connection refused
2024/05/23 20:01 bpf 8d00547ea875 8f98448e .config console log report [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce bpf test error: SYZFATAL: failed to connect to host: dial tcp IP:NUM: connect: connection refused
2024/05/22 14:47 bpf 8d00547ea875 4d098039 .config console log report [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce bpf test error: SYZFATAL: failed to connect to host: dial tcp IP:NUM: connect: connection refused
* Struck through repros no longer work on HEAD.