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.
17 files changed
tree: 488d071d79b6c58254741a8de91190071698b649
  1. .clang-format
  2. .gitignore
  3. .golangci.yml
  4. .travis.yml
  5. AUTHORS
  6. CODE_OF_CONDUCT.md
  7. CONTRIBUTORS
  8. Godeps/
  9. LICENSE
  10. Makefile
  11. README.md
  12. dashboard/
  13. docs/
  14. executor/
  15. fuzzbuzz.yaml
  16. fuzzit.sh
  17. pkg/
  18. prog/
  19. sys/
  20. syz-ci/
  21. syz-fuzzer/
  22. syz-hub/
  23. syz-manager/
  24. tools/
  25. vendor/
  26. vm/
README.md

syzkaller - kernel fuzzer

Build Status fuzzit Go Report Card Coverage Status GoDoc License

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.

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

External Articles

Disclaimer

This is not an official Google product.