syzkaller/syz-fuzzer
Dmitry Vyukov ae8bdb5058 syz-fuzzer: don't crash on commit mismatch
We now check for manager-fuzzer-executor commit mismatch (see Manager.Check).
But in some cases commit mismatch is not detected gracefully, and instead
leads to panics in fuzzer. Namely, when -enabled_syscalls fuzzer flag includes
large syscalls numbers, so large that they are no present at all in the an old
revision that fuzzer uses, in such case fuzzer panics.

Notify manager about invalid calls instead.

Fixes #464
2018-06-11 12:12:01 +03:00
..
fuzzer_freebsd.go syz-fuzzer: wipe all global state 2017-12-19 10:53:39 +01:00
fuzzer_fuchsia.go syz-fuzzer: wipe all global state 2017-12-19 10:53:39 +01:00
fuzzer_linux.go syz-fuzzer: fix kcov detection for cross-arch testing 2018-04-27 15:42:48 +02:00
fuzzer_netbsd.go syz-fuzzer: wipe all global state 2017-12-19 10:53:39 +01:00
fuzzer_windows.go syz-fuzzer: wipe all global state 2017-12-19 10:53:39 +01:00
fuzzer.go syz-fuzzer: don't crash on commit mismatch 2018-06-11 12:12:01 +03:00
proc.go syz-fuzzer: write programs directly to stdout 2018-06-06 20:39:36 +02:00
testing.go gometalinter: check dot imports 2018-05-03 14:41:34 +02:00
workqueue.go syz-fuzzer: don't break syscalls during minimization 2018-02-19 21:48:20 +01:00