QEMU coverage builds have been failing for a long time. Maybe this is
occuring due to the inputs being too large and timing out. Limit the
input size, in an attempt to fix this.
Signed-off-by: Alexander Bulekov <alxndr@bu.edu>
We don't do any internal tests using honggfuzz, and our code is highly
unlikely to work with honggfuzz in the current shape. All of the
true-positive bugs seem to be libfuzzer bugs.
Lets disable honggfuzz, to avoid wasting resources. We will try to get
afl++ working, before taking another look at honggfuzz.
Signed-off-by: Alexander Bulekov <alxndr@bu.edu>
In qemu/qemu@fff7111 we added configurations for fuzzing virtio-9p
devices. However, these fuzzers are presently stalled on oss-fuzz,
because the build image doesn't have the necessary libattr, and
libcap-ng libraries. Fix that.
Signed-off-by: Alexander Bulekov <alxndr@bu.edu>
As of QEMU's 09e93326e4 ("build: replace ninjatool with ninja"), QEMU
now requires ninja instead of ninjatool for builds.
Signed-off-by: Alexander Bulekov <alxndr@bu.edu>
* QEMU: Add fuzz target build scripts
Signed-off-by: Alexander Bulekov <alxndr@bu.edu>
* QEMU: Disable AFL and MSan in project.yaml
We can't link against OSS-Fuzz' afl driver as it is not compiled with
-fPIC. Additionally, it appears that we trigger some false-positives
with MemorySanitizer, since we don't instrument all of the libraries.
Disable AFL and MemorySanitizer, for now.
Signed-off-by: Alexander Bulekov <alxndr@bu.edu>
Alexander Bulekov