I would also like to point out that the wireshark corpus will make testing more efficient. I am currently using a corpus from here [1] and it covers code more quickly. Please bear in mind that this particular payload corpus contains the packet payload (hence suitable for our testcases) but is limited to 40 something files only. Would be nice to find a larger corpus if one exists.
[1]: https://bitbucket.org/jwzawadzki/wireshark-fuzzdb/src/98fa5ba9a4c27a2fbcbe68bc43f696cfa295046e/samples/?at=master Regards, Bhargava On 08/31/2017 11:55 PM, Bhargava Shastry wrote: > This is a nice test case for upstream. Am currently running on 8 cores, > no crashes in the flow_extract API so far. > > Regards, > Bhargava > > On 08/31/2017 11:03 PM, Ben Pfaff wrote: >> int LLVMFuzzerTestOneInput(const uint8_t* data, size_t size) >> { >> struct dp_packet packet; >> dp_packet_use_const(&packet, data, size); >> >> struct flow flow; >> flow_extract(&packet, &flow); >> >> return 0; >> } > -- Bhargava Shastry <bshas...@sec.t-labs.tu-berlin.de> Security in Telecommunications TU Berlin / Telekom Innovation Laboratories Ernst-Reuter-Platz 7, Sekr TEL 17 / D - 10587 Berlin, Germany phone: +49 30 8353 58235 Keybase: https://keybase.io/bshastry _______________________________________________ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev
