Re: [PATCH] fuzz: pass failures from child process into libfuzzer engine

  06.12.2021, 19:35, "Alexander Bulekov" :On 211205 1917, Konstantin Khlebnikov wrote: Fuzzer is supposed to stop when first bug is found and report failure. Present fuzzers fork new child at each iteration to isolate side-effects. But child's exit code is ignored, i.e. libfuzzer does not see any c

Re: [PATCH] fuzz: pass failures from child process into libfuzzer engine

On 211206 2348, Konstantin Khlebnikov wrote: >  >  >06.12.2021, 19:35, "Alexander Bulekov" <[1]alx...@bu.edu>: > > On 211205 1917, Konstantin Khlebnikov wrote: > > Fuzzer is supposed to stop when first bug is found and report >failure. > Present fuzzers fo

Re: [PATCH] fuzz: pass failures from child process into libfuzzer engine

  06.12.2021, 19:35, "Alexander Bulekov" :On 211205 1917, Konstantin Khlebnikov wrote: Fuzzer is supposed to stop when first bug is found and report failure. Present fuzzers fork new child at each iteration to isolate side-effects. But child's exit code is ignored, i.e. libfuzzer doe

Re: [PATCH] fuzz: pass failures from child process into libfuzzer engine

On 211205 1917, Konstantin Khlebnikov wrote: > Fuzzer is supposed to stop when first bug is found and report failure. > Present fuzzers fork new child at each iteration to isolate side-effects. > But child's exit code is ignored, i.e. libfuzzer does not see any crashes. > > Right now virtio-net fu

[PATCH] fuzz: pass failures from child process into libfuzzer engine

Fuzzer is supposed to stop when first bug is found and report failure. Present fuzzers fork new child at each iteration to isolate side-effects. But child's exit code is ignored, i.e. libfuzzer does not see any crashes. Right now virtio-net fuzzer instantly falls on assert in iov_copy and dumps cr