commit | 37dc03de04826cc0d5d1e3699832b0a3113d40af | [log] [tgz] |
---|---|---|
author | Dmitry Vyukov <dvyukov@google.com> | Fri Oct 18 08:12:06 2019 +0200 |
committer | Dmitry Vyukov <dvyukov@google.com> | Tue Oct 22 09:52:16 2019 +0200 |
tree | 488d071d79b6c58254741a8de91190071698b649 | |
parent | c59a7cd871bf29d123481b2e5b0bd739b064f15f [diff] |
pkg/report: improve parsing of task hung reports The problem with task hung reports is that they manifest at random victim stacks, rather at the root cause stack. E.g. if there is something wrong with RCU subsystem, we are getting hangs all over the kernel on all synchronize_* calls. So before resotring to the common logic of skipping some common frames, we look for 2 common buckets: hangs on synchronize_rcu and hangs on rtnl_lock and group these together.
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.