Bhargava Shastry <[email protected]> writes: > Hi all, > > oss-fuzz corpus (test inputs synthesized by the fuzzer) comprises two > classes of inputs: crashing and non-crashing-but-new-coverage-yielding. > > At the moment, Open vSwitch performs regression testing using > **crashing** test inputs only [1]. > > [1]: https://github.com/openvswitch/ovs/tree/master/tests/fuzz-regression > > However, adding non-crashing test inputs generated by the fuzzer to this > set may be useful to catch bugs that are not necessarily regressions of > known bugs but bugs in program paths that have already been covered > during fuzz testing.
This is a good idea. Any time we can trap bugs, even if they don't create faults, is a good thing(tm). :) > If you like this idea, I have an initial proposal. What we could do is > use this "driver" [2] for each of the fuzzer targets to drive regression > testing on the entire fuzzer corpus. > > [2]: > https://github.com/llvm-mirror/compiler-rt/blob/master/lib/fuzzer/standalone/StandaloneFuzzTargetMain.c > > The fuzzer corpus may be downloaded by oss-fuzz contact points (e.g., > Ben Pfaff, Justin Pettit etc.) from Google Cloud via a program called > gsutil that is shipped with Google Cloud SDK. This would need to be > updated from time to time, but this is very easy (`gsutil sync` is > sufficient). Why should this only be available to small group of people? Is it possible to expose this to everyone? That way developers could take advantage of the fuzzer for their own internal testing while developing patches. Did I misunderstand it? > The plan is to have a PR that includes the corpus obtained via Google > cloud, standalone drivers, and some sort of regression test automation > for all the fuzzer targets. I would prefer if it were sent to the list, and have updates also come via the list. But that's just me. > I am interested in contributing to this effort, should you decide to go > forward with it. Looking forward to feedback. Thanks for all of the fuzzer effort, Bhargava! > Best, > Bhargava _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
