executor: only report unknown setsid errors

Unlike linux the BSDs used to check the result of setsid.

This suddenly became a problem a couple of weeks ago. It's hard
to figure out why because there was a number of problems in the
area preventing the test from working:

gmake executor execprog && \
./bin/openbsd_amd64/syz-execprog -stress -executor ./bin/openbsd_amd64/syz-executor

At least with this change the test above successfully executes some
coverage and exits cleanly.
1 file changed
tree: 01464029c372ec326834840ce8790a8cd2c59ecd
  1. .github/
  2. dashboard/
  3. docs/
  4. executor/
  5. pkg/
  6. prog/
  7. sys/
  8. syz-ci/
  9. syz-hub/
  10. syz-manager/
  11. syz-verifier/
  12. tools/
  13. vendor/
  14. vm/
  15. .clang-format
  16. .gitattributes
  17. .gitignore
  18. .golangci.yml
  19. AUTHORS
  20. CODE_OF_CONDUCT.md
  21. CONTRIBUTORS
  22. go.mod
  23. go.sum
  24. LICENSE
  25. Makefile
  26. 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: FreeBSD, Fuchsia, gVisor, Linux, NetBSD, OpenBSD, Windows.

Mailing list: syzkaller@googlegroups.com (join on web or by email).

Found bugs: 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: Darwin/XNU, FreeBSD, Fuchsia, NetBSD, OpenBSD, Starnix, Windows, gVisor. Akaros,

Disclaimer

This is not an official Google product.