syzbot


gvisor boot error: init process did not start

Status: closed as invalid on 2018/12/12 10:27
First crash: 2338d, last: 2331d
Similar bugs (5)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
gvisor gvisor boot error: init process did not start (2) 3626 1536d 1959d 0/26 closed as invalid on 2020/09/13 08:21
gvisor gvisor boot error: init process did not start (5) 41 502d 630d 26/26 fixed on 2023/10/23 20:48
gvisor gvisor boot error: init process did not start (6) 54 363d 363d 0/26 auto-obsoleted due to no activity on 2024/01/17 19:39
gvisor gvisor boot error: init process did not start (4) 6 1055d 1069d 0/26 auto-closed as invalid on 2022/04/06 03:53
gvisor gvisor boot error: init process did not start (3) 882 1343d 1519d 0/26 auto-closed as invalid on 2021/05/22 19:22
Crashes (3):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2018/07/09 19:04 https://gvisor.googlesource.com/gvisor master 0dedac637ff9 f25e5770 .config console log ci-gvisor-kvm-direct-sandbox
2018/07/03 17:53 https://gvisor.googlesource.com/gvisor master 4500155ffc5e b9f93868 .config console log ci-gvisor-kvm-direct-sandbox
2018/07/02 22:03 https://gvisor.googlesource.com/gvisor master 126296ce2adc b9f93868 .config console log ci-gvisor-kvm-proxy-overlay-sandbox
* Struck through repros no longer work on HEAD.