syzbot

 sign-in | mailing list | source | docs
🐞 Open [38] 🐞 Fixed [434] 🐞 Invalid [316] 📈 Kernel Health 📈 Bug Lifetimes 📈 Fuzzing 📈 Crashes 💬 Send us feedback

FATAL ERROR: retrieving stacks: connecting to control server at pid X: connection refused

Status: closed as invalid on 2019/08/13 21:43
Reported-by: syzbot+8c6dda2c691c08ec2b02@syzkaller.appspotmail.com
First crash: 1897d, last: 1897d

Sample crash report:
W0222 21:17:15.444229   64595 x:0] FATAL ERROR: retrieving stacks: connecting to control server at PID 9599: connection refused
retrieving stacks: connecting to control server at PID 9599: connection refused
D0222 21:17:15.524295    9359 x:0] Killing gofer for container "ci-gvisor-kvm-direct-sandbox-1", PID: 9524
I0222 21:17:15.626282    9359 x:0] Exiting with status: 11

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2019/02/22 21:17 https://gvisor.googlesource.com/gvisor master b2a5ad047a26 baad4d36 .config console log report ci-gvisor-kvm-direct-sandbox
* Struck through repros no longer work on HEAD.