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 [13]
🐞 Fixed [581]
🐞 Invalid [438]
≡
Crashes
📈
Graphs
Kernel Health
Bugs/Month
Bug Lifetimes
Bug Resolution Rate
Fuzzing
💬
Send us feedback
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: 676d, last: 676d
▶
▼
Similar bugs (4)
Kernel
Title
Rank
🛈
Repro
Cause bisect
Fix bisect
Count
Last
Reported
Patched
Status
gvisor
init process did not start (5)
-1
1333
27d
66d
0/26
moderation: reported on 2026/07/17 14:17
gvisor
init process did not start (3)
-1
1
642d
635d
0/26
auto-obsoleted due to no activity on 2025/03/18 05:30
gvisor
init process did not start (4)
-1
11
462d
532d
0/26
auto-obsoleted due to no activity on 2025/09/14 15:32
gvisor
init process did not start
-1
2
830d
830d
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.