[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 00/10] Retire Fork-Based Fuzzing
From: |
Alexander Bulekov |
Subject: |
Re: [PATCH 00/10] Retire Fork-Based Fuzzing |
Date: |
Mon, 6 Feb 2023 09:09:07 -0500 |
On 230205 1139, Philippe Mathieu-Daudé wrote:
> On 5/2/23 05:29, Alexander Bulekov wrote:
>
> > * Some device do not completely reset their state. This can lead to
> > non-reproducible crashes. However, in my local tests, most crashes
> > were reproducible. OSS-Fuzz shouldn't send us reports unless it can
> > consistently reproduce a crash.
>
> These devices are buggy, hard/cold reset should be reproducible.
Agreed. However I don't think the fuzzer is tailored to report these
types of bugs. OSS-Fuzz will just see that some crashes/inputs are not
reproducible. I have been thinking about ways to make the fuzzer report
incomplete VMStateDescriptions. Maybe something similar can be done for
reboots.
-Alex
>
> > * In theory, the corpus-format should not change, so the existing
> > corpus-inputs on OSS-Fuzz will transfer to the new reset()-able
> > fuzzers.
>
- Re: [PATCH 06/10] fuzz/virtio-net: remove fork-based fuzzer, (continued)
- [PATCH 07/10] fuzz/virtio-blk: remove fork-based fuzzer, Alexander Bulekov, 2023/02/04
- [PATCH 08/10] fuzz/i440fx: remove fork-based fuzzer, Alexander Bulekov, 2023/02/04
- [PATCH 10/10] docs/fuzz: remove mentions of fork-based fuzzing, Alexander Bulekov, 2023/02/04
- [PATCH 09/10] fuzz: remove fork-fuzzing scaffolding, Alexander Bulekov, 2023/02/04
- Re: [PATCH 00/10] Retire Fork-Based Fuzzing, Philippe Mathieu-Daudé, 2023/02/05
- Re: [PATCH 00/10] Retire Fork-Based Fuzzing,
Alexander Bulekov <=
- Re: [PATCH 00/10] Retire Fork-Based Fuzzing, Alexander Bulekov, 2023/02/12
- Re: [PATCH 00/10] Retire Fork-Based Fuzzing, Stefan Hajnoczi, 2023/02/14