syzbot


gvisor boot error: init process did not start (4)

Status: auto-closed as invalid on 2022/04/06 03:53
Reported-by: syzbot+cb1ad93ec0aaaa91c528@syzkaller.appspotmail.com
First crash: 1076d, last: 1055d
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 (3) 882 1343d 1519d 0/26 auto-closed as invalid on 2021/05/22 19:22
gvisor gvisor boot error: init process did not start 3 2331d 2338d 0/26 closed as invalid on 2018/12/12 10:27
Crashes (6):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2022/01/06 03:52 gvisor 66ad3a56574a 6acc789a .config console log ci-gvisor-ptrace-1-cover gvisor boot error: init process did not start
2022/01/06 03:52 gvisor 66ad3a56574a 6acc789a .config console log ci-gvisor-ptrace-1-cover gvisor boot error: init process did not start
2021/12/22 23:24 gvisor db3d9988c8fe 6caa12e4 .config console log ci-gvisor-ptrace-1 gvisor boot error: init process did not start
2021/12/22 23:24 gvisor db3d9988c8fe 6caa12e4 .config console log ci-gvisor-ptrace-1 gvisor boot error: init process did not start
2021/12/15 16:16 gvisor 6f0a4ec86a3e f752fb53 .config console log ci-gvisor-ptrace-2 gvisor boot error: init process did not start
2021/12/15 16:16 gvisor 6f0a4ec86a3e f752fb53 .config console log ci-gvisor-ptrace-2 gvisor boot error: init process did not start
* Struck through repros no longer work on HEAD.