commit | da505f84d3e8fc3bb7c54fea76eb5574987ee01a | [log] [tgz] |
---|---|---|
author | Dmitry Vyukov <dvyukov@google.com> | Wed Nov 06 11:39:02 2019 +0100 |
committer | Dmitry Vyukov <dvyukov@google.com> | Wed Nov 06 11:41:05 2019 +0100 |
tree | 1744e28afcc5c1ee6ab874000bac35c53bc598dd | |
parent | 424cf6e8a12577719dc310bce2cce2a91723cf54 [diff] |
pkg/report: detect syzkaller panics in lost connection bugs Some syzkaller panics happen due to memory corruptions, but it still would be useful at least to get some visibility into these crashes. On some OSes we actualy already detect them as they have "panic:" oops pattern, but not e.g. on linux. Fixes #318
syzkaller
is an unsupervised coverage-guided kernel fuzzer.
Supported OSes: Akaros
, FreeBSD
, Fuchsia
, gVisor
, Linux
, NetBSD
, OpenBSD
, Windows
.
Mailing list: syzkaller@googlegroups.com (join on web or by email).
Found bugs: Akaros, Darwin/XNU, FreeBSD, Linux, NetBSD, OpenBSD, Windows.
Initially, syzkaller was developed with Linux kernel fuzzing in mind, but now it's being extended to support other OS kernels as well. Most of the documentation at this moment is related to the Linux kernel. For other OS kernels check: Akaros, Darwin/XNU, FreeBSD, Fuchsia, NetBSD, OpenBSD, Windows, gVisor.
This is not an official Google product.