commit | 0dbba7ad6ccbcb80641d05e55214eafd098883c4 | [log] [tgz] |
---|---|---|
author | Mark Johnston <markjdb@gmail.com> | Mon Mar 18 13:41:53 2019 -0400 |
committer | Dmitry Vyukov <dvyukov@google.com> | Tue Mar 19 10:26:46 2019 +0100 |
tree | b1999c319f2eb54cb4f22f86073fdaa3a6fd32a2 | |
parent | 46264c32592e5b2b959e3290bd0b8305ecec58db [diff] |
sys/targets: use kernel.full instead of kernel.debug The latter contains only debug symbols and is meant to be used with the kernel executable. That is, the kernel executable contains a .gnu_debuglink pointer to kernel.debug. kernel.full contains everything, including a copy of the kernel's text section, which we want when enumerating __sanitizer_cov_trace_pc() calls for a coverage report.
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.