syzbot


linux-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: 23d, last: 22d

Sample crash report:
Warning: Permanently added '10.128.0.7' (ED25519) to the list of known hosts.
2024/05/23 16:00:04 fuzzer started
2024/05/23 16:00:04 dialing manager at 10.128.0.169:30011
2024/05/23 16:00:04 SYZFATAL: failed to connect to host: dial tcp 10.128.0.169:30011: connect: connection refused 

Crashes (3):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/05/23 16:11 linux-next 3689b0ef08b7 8f98448e .config console log report [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root linux-next test error: SYZFATAL: failed to connect to host: dial tcp IP:NUM: connect: connection refused
2024/05/23 02:35 linux-next 3689b0ef08b7 4d098039 .config console log report [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root linux-next test error: SYZFATAL: failed to connect to host: dial tcp IP:NUM: connect: connection refused
2024/05/22 12:15 linux-next 8314289a8d50 4d098039 .config console log report [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root linux-next test error: SYZFATAL: failed to connect to host: dial tcp IP:NUM: connect: connection refused
* Struck through repros no longer work on HEAD.