Using syzkaller, part 4: Driver fuzzing

Paf — Sat, 27 Jun 2020 15:10:17 +0000

It also seems especially important to have different families/types of fuzzers - they will walk the (extremely broad) parameter spaces in different ways, finding (ideally) different types of issue. This seems especially important for fuzzing suites, whereas the benefit of having two different (for example) POSIX correctness suites seems likely to be less. (Not that the benefit of that would be zero)

Using syzkaller, part 4: Driver fuzzing

deater — Fri, 26 Jun 2020 19:17:59 +0000

I get this a lot too. "why use perf_fuzzer when syzkaller exists?"

perf_fuzzer finds bugs that syzkaller doesn't, in part because by being aware of how the syscall works you can focus the (enormous) search space to combinations of inputs more likely to trigger errors.

LWN: Comments on "Using syzkaller, part 4: Driver fuzzing"

Using syzkaller, part 4: Driver fuzzing

Using syzkaller, part 4: Driver fuzzing