Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The size of the input.not_interesting folder is growing rapidly #10

Open
Yu3H0 opened this issue Jul 25, 2023 · 1 comment
Open

The size of the input.not_interesting folder is growing rapidly #10

Yu3H0 opened this issue Jul 25, 2023 · 1 comment

Comments

@Yu3H0
Copy link

Yu3H0 commented Jul 25, 2023

hello, I run ViDeZZo through the following command:

/videzzo_qemu/out-san/qemu-videzzo-i386-target-videzzo-fuzz-ehci  ./input/

the input folder holds the initial seed

But in the same level directory, there is an input.not_interesting folder that grows in size very quickly when fuzzing and quickly fills up my disk.

I want to know how to deal with it. Thanks.

@cyruscyliu
Copy link
Collaborator

cyruscyliu commented Jul 25, 2023

ViDeZZo currently enables persisting fuzzing. Testcases in input.not_interesting/ are necessary to reproduce crashes if any. The size grows very quickly, which is normal, and you need larger storage for that. Based on my experience, also depending on the target, you'd better have 1TB for 1-hour fuzzing.

This is what I recommend now. Run the fuzzing campaign without the corpus for a long time and check if there is any crash. If so, enable the corpus to reproduce the crash on a machine with large storage. This strategy is enough for our research but I know it is an open issue.

Two technical ways to fix this issue.

  • Enable the fork server. I was doing this but haven't finished it. I need to sync the coverage/feature from the child processes to the parent process. Then I have to fine-tune the performance issue as using a fork server is way too slow.
  • Develop a good way to record part of the test cases. This is a research question and I haven't had a good idea.

Looking forward to discussing more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants