tools/syz-execprog: use more precise addresses when collecting coverage

Make two improvements to addresses obtained from kcov:
 - call backend.PreviousInstructionPC() so that they point to the
   __sanitizer_cov_trace_pc calls;
 - read the top 32 bits of the kernel addresses from /proc/kallsyms
   instead of using the hardcoded 0xffffffff value
1 file changed
tree: 8d0b5ff4f35f36a1002b34a77eb58a5b036d4a93
  1. .github/
  2. dashboard/
  3. docs/
  4. executor/
  5. pkg/
  6. prog/
  7. sys/
  8. syz-ci/
  9. syz-fuzzer/
  10. syz-hub/
  11. syz-manager/
  12. syz-runner/
  13. syz-verifier/
  14. tools/
  15. vendor/
  16. vm/
  17. .clang-format
  18. .gitattributes
  19. .gitignore
  20. .golangci.yml
  21. AUTHORS
  22. CODE_OF_CONDUCT.md
  23. codecov.yml
  24. CONTRIBUTORS
  25. go.mod
  26. go.sum
  27. LICENSE
  28. Makefile
  29. README.md
README.md

syzkaller - kernel fuzzer

CI Status OSS-Fuzz Go Report Card Coverage Status GoDoc License

syzkaller ([siːzˈkɔːlə]) 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, Starnix, Windows, gVisor.

Disclaimer

This is not an official Google product.