syzbot


init process did not start (4)

Status: moderation: reported on 2025/04/06 19:41
Reported-by: syzbot+bb949ef9dd7d16dcb1e7@syzkaller.appspotmail.com
First crash: 44d, last: 42d
Similar bugs (3)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
gvisor init process did not start (2) 1 180d 173d 0/26 closed as invalid on 2024/12/12 23:51
gvisor init process did not start (3) 1 146d 139d 0/26 auto-obsoleted due to no activity on 2025/03/18 05:30
gvisor init process did not start 2 334d 334d 26/26 fixed on 2024/06/18 07:55
Crashes (3):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/03/31 20:35 gvisor 8221e477b5c4 36d76a97 ci-gvisor-systrap-1 init process did not start
2025/03/30 18:38 gvisor d06b27e25f95 d3999433 .config console log ci-gvisor-ptrace-1-race-cover init process did not start
2025/03/30 18:38 gvisor d06b27e25f95 d3999433 console log ci-gvisor-systrap-1 init process did not start
* Struck through repros no longer work on HEAD.