Dmitry Vyukov 6839de7050 pkg/report: fix corrupted stack trace checking
We started detecting all kernel reboots as corrupted,
because we considered that after any "Allocated" line
a stack trace should follow.
Kernel boot output now contains:
ima: Allocated hash algorithm: sha256
and there is no stack trace after that.

1. Refine stack trace regexps (we actually want to look for
"Allocated by task PID:" lines).
2. Don't check stacks if report format says that it
does not contain stacks.
2018-11-22 07:40:50 +01:00
2018-11-21 05:56:43 +01:00
2018-11-21 07:27:04 +01:00
2017-07-28 13:25:48 +02:00
2017-06-13 15:55:31 +02:00
2015-10-12 10:16:57 +02:00
2018-10-01 11:37:27 +02:00

syzkaller - kernel fuzzer

Build Status Go Report Card License

syzkaller is an unsupervised coverage-guided kernel fuzzer. Linux kernel fuzzing has the most support, akaros, freebsd, fuchsia, netbsd, windows and gvisor are supported to varying degrees.

The project mailing list is syzkaller@googlegroups.com. You can subscribe to it with a google account or by sending an email to syzkaller+subscribe@googlegroups.com.

List of found bugs.

Documentation

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, FreeBSD, Fuchsia, NetBSD, OpenBSD, Windows, gVisor.

External Articles

Disclaimer

This is not an official Google product.

Description
syzkaller is an unsupervised coverage-guided kernel fuzzer
Readme Pixar 180 MiB
Languages
Go 77.1%
C 11%
Roff 5.3%
C++ 2.2%
Shell 1.5%
Other 2.8%