init process did not start (2)

Status: closed as invalid on 2024/12/12 23:51
Reported-by: syzbot+c5c7698c416abf51d283@syzkaller.appspotmail.com
First crash: 734d, last: 734d
▶ ▼ Similar bugs (4)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
gvisor init process did not start (5) -1 1362 19d 124d 0/26 moderation: reported on 2026/07/17 14:17
gvisor init process did not start (3) -1 1 700d 693d 0/26 auto-obsoleted due to no activity on 2025/03/18 05:30
gvisor init process did not start (4) -1 11 520d 591d 0/26 auto-obsoleted due to no activity on 2025/09/14 15:32
gvisor init process did not start -1 2 888d 888d 26/26 fixed on 2024/06/18 07:55
Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/11/14 11:50 gvisor 4f92c2873fd6 a8c99394 .config console log ci-gvisor-arm64-systrap-1-cover init process did not start
* Struck through repros no longer work on HEAD.