dfc86c0f25
By default, -fsanitize=fuzzer instruments all code with coverage information. However, this means that libfuzzer will track coverage over hundreds of source files that are unrelated to virtual-devices. This means that libfuzzer will optimize inputs for coverage observed in timer code, memory APIs etc. This slows down the fuzzer and stores many inputs that are not relevant to the actual virtual-devices. With this change, clang versions that support the "-fsanitize-coverage-allowlist" will only instrument a subset of the compiled code, that is directly related to virtual-devices. Signed-off-by: Alexander Bulekov <alxndr@bu.edu> Reviewed-by: Darren Kenny <darren.kenny@oracle.com>
16 lines
525 B
Plaintext
16 lines
525 B
Plaintext
# Code that we actually want the fuzzer to target
|
|
# See: https://clang.llvm.org/docs/SanitizerCoverage.html#disabling-instrumentation-without-source-modification
|
|
#
|
|
src:*/hw/*
|
|
src:*/include/hw/*
|
|
src:*/slirp/*
|
|
src:*/net/*
|
|
|
|
# We don't care about coverage over fuzzer-specific code, however we should
|
|
# instrument the fuzzer entry-point so libFuzzer always sees at least some
|
|
# coverage - otherwise it will exit after the first input
|
|
src:*/tests/qtest/fuzz/fuzz.c
|
|
|
|
# Enable instrumentation for all functions in those files
|
|
fun:*
|