syzbot

 sign-in | mailing list | source | docs
🐞 Open [1433]
≡ Subsystems
🐞 Fixed [6905]
🐞 Invalid [17978]
⬇ Missing Backports [223]
≡ Crashes
Kernel Health Bugs/Month Bug Lifetimes Fuzzing
Total Repo Heatmap Subsystems Heatmap
💬 Send us feedback

SYZFAIL: child failed (3)

Status: auto-obsoleted due to no activity on 2025/06/28 15:48
First crash: 315d, last: 315d
▶ ▼ Similar bugs (4)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream SYZFAIL: child failed (4) -1 1 112d 112d 0/29 auto-obsoleted due to no activity on 2026/01/18 00:54
upstream SYZFAIL: child failed -1 syz error error 63 961d 1743d 0/29 auto-obsoleted due to no activity on 2023/11/14 01:44
upstream SYZFAIL: child failed (2) -1 3 528d 542d 0/29 auto-obsoleted due to no activity on 2024/11/28 05:59
android-5-10 SYZFAIL: child failed -1 syz error error 1 497d 1506d 0/2 auto-obsoleted due to no activity on 2024/12/28 11:13

Sample crash report:
SYZFAIL: child failed
 (errno 0: Success)
EXT4-fs (loop0): unmounting filesystem 00000000-0000-0000-0000-000000000000.

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/03/30 15:47 upstream 93d52288679e d3999433 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root SYZFAIL: child failed
* Struck through repros no longer work on HEAD.