Copy fuzzers from github.com/cncf/cncf-fuzzing#7123
Copy fuzzers from github.com/cncf/cncf-fuzzing#7123dmcgowan merged 2 commits intocontainerd:mainfrom
Conversation
|
Skipping CI for Draft Pull Request. |
kzys
force-pushed
the
fuzz
branch
7 times, most recently
from
7628922 to
fe4ba1c
Compare
|
@AdamKorcz Please take a look. |
|
@AdamKorcz Is it possible to measure the efficiency (e.g. # of lines covered / iterations?) of a fuzzer? I'm wondering about https://github.com/cncf/cncf-fuzzing/blob/c402ef33d7a399d1c00c009d51df910e30dfe00a/projects/containerd/containerd_import_structured_fuzzer.go#L73-L79. Does it make sense to have both and containerd_import_structured_fuzzer.go? |
The simplest test is to run these fuzzers over a defined time (for example 2 hours) and observe its coverage. As far as I remember, the structured fuzzer outperforms the non-structured one significantly. However, there might be value in having a fuzzer that generates more random input than the structured one, for example if the structured one does not reach all code. |
Signed-off-by: Kazuyoshi Kato <[email protected]>
This commit copies the fuzzers from the repository except for containerd_import_structured_fuzzer.go. Signed-off-by: Kazuyoshi Kato <[email protected]>
|
This one is ready for review. I will work on containerd_import_structured_fuzzer.go in a different PR since this PR is already big. |
They are copied to containerd's repos in containerd/containerd#7123. Signed-off-by: Kazuyoshi Kato <[email protected]>
5 participants
This commit copies the fuzzers from the repository except for
containerd_import_structured_fuzzer.go.
Signed-off-by: Kazuyoshi Kato [email protected]