syzbot


gvisor boot error (2)

Status: closed as invalid on 2018/12/12 10:27
First crash: 2224d, last: 2176d
Similar bugs (3)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
gvisor gvisor boot error (3) 4 2174d 2175d 0/26 fixed on 2018/12/14 04:14
gvisor gvisor boot error (4) 5 2170d 2083d 0/26 auto-closed as invalid on 2019/06/16 09:52
gvisor gvisor boot error 1911 2252d 2329d 0/26 fixed on 2018/10/15 18:31

Sample crash report:
FATAL ERROR: error running container: error creating container: error creating control server socket for sandbox "ci-gviW1212 09:26:11.861839    6603 x:0] FATAL ERROR: error running container: error creating container: error creating control server socket for sandbox "ci-gvisor-ptrace-proxy-sandbox-race-test-1": address already in use
error running container: error creating container: error creating control server socket for sandbox "ci-gvisor-ptrace-proxy-sandbox-race-test-1": address already in use

Crashes (4):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2018/12/12 09:26 https://gvisor.googlesource.com/gvisor master a2c868a098fc c3b10a5d .config console log report ci-gvisor-ptrace-proxy-sandbox-race
2018/11/01 02:55 https://gvisor.googlesource.com/gvisor master c2249d647234 1f38e9ae .config console log report ci-gvisor-kvm-proxy-overlay-sandbox
2018/10/30 23:11 https://gvisor.googlesource.com/gvisor master 245d81561b52 4ccf7bb4 .config console log report ci-gvisor-kvm-direct-sandbox
2018/10/24 22:56 https://gvisor.googlesource.com/gvisor master e7191f058f55 24fa2ad8 .config console log report ci-gvisor-kvm-direct-overlay-host-race
* Struck through repros no longer work on HEAD.