syzbot
Android 5.10
Android 5.15
Android 5.4
Android 6.1
Android 6.12
FreeBSD
Linux
Linux 5.15
Linux 6.1
Linux 6.6
NetBSD
OpenBSD
gVisor
sign-in
|
mailing list
|
source
|
docs
🐞 Open [17]
🐞 Fixed [585]
🐞 Invalid [439]
≡
Crashes
📈
Graphs
Kernel Health
Bugs/Month
Bug Lifetimes
Bug Resolution Rate
Fuzzing
💬
Send us feedback
init process did not start
Status: fixed on 2024/06/18 07:55
Fix commit:
80a501d8cc23
Avoid redundant work in `bpf.optimizeJumpsToSmallestSetOfReturns`.
First crash: 888d, last: 888d
▶
▼
Similar bugs (4)
Kernel
Title
Rank
🛈
Repro
Cause bisect
Fix bisect
Count
Last
Reported
Patched
Status
gvisor
init process did not start (2)
-1
1
734d
727d
0/26
closed as invalid on 2024/12/12 23:51
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
Crashes (2):
Time
Kernel
Commit
Syzkaller
Config
Log
Report
Syz repro
C repro
VM info
Assets
(
help?
)
Manager
Title
2024/06/13 07:25
gvisor
bb242cb31035
2aa5052f
.config
console log
ci-gvisor-arm64-systrap-1-race-cover
init process did not start
2024/06/13 07:25
gvisor
bb242cb31035
2aa5052f
.config
console log
ci-gvisor-arm64-systrap-1-race-cover
init process did not start
*
Struck through
repros no longer work on HEAD.