syzbot

 sign-in | mailing list | source | docs
🐞 Open [1260] ≡ Subsystems 🐞 Fixed [5427] 🐞 Invalid [12853] ⬇ Missing Backports [106] 📈 Kernel Health 📈 Bugs/Month 📈 Bug Lifetimes 📈 Fuzzing 📈 Crashes 📈 Coverage 💬 Send us feedback

net-next 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: 32d, last: 32d

Sample crash report:
Warning: Permanently added '10.128.10.51' (ED25519) to the list of known hosts.
2024/05/24 02:00:21 fuzzer started
2024/05/24 02:00:22 dialing manager at 10.128.0.169:30019
2024/05/24 02:00:22 SYZFATAL: failed to connect to host: dial tcp 10.128.0.169:30019: 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 02:14 net-next 66ad4829ddd0 8f98448e .config console log report [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce net-next test error: SYZFATAL: failed to connect to host: dial tcp IP:NUM: connect: connection refused
2024/05/23 22:59 net-next 66ad4829ddd0 8f98448e .config console log report [disk image] [vmlinux] [kernel image] ci2-upstream-net-next-test-gce net-next test error: SYZFATAL: failed to connect to host: dial tcp IP:NUM: connect: connection refused
2024/05/23 21:20 net-next 66ad4829ddd0 4c2072ee .config console log report [disk image] [vmlinux] [kernel image] ci2-upstream-net-next-test-gce net-next test error: SYZFATAL: failed to connect to host: dial tcp IP:NUM: connect: connection refused
* Struck through repros no longer work on HEAD.