search

srlabs / ziggy

A multi-fuzzer management utility for all of your Rust fuzzing needs 🧑‍🎤
Apache License 2.0
59 stars 6 forks source link

Introduce coverage worker #96

Open R9295 opened 2 months ago

R9295 commented 2 months ago

Implements and closes #75

TODO

R9295 commented 2 months ago

One doubt I have is if fs::read_dir's iterator will also continue to yield entries created after it was called (probably?). In that case we may never get to generate the report and may just be stuck running new entries.

vanhauser-thc commented 2 months ago

One doubt I have is if fs::read_dir's iterator will also continue to yield entries created after it was called (probably?). In that case we may never get to generate the report and may just be stuck running new entries.

Test it?

also I deduct this pr still needs quite some real world testing before we merge it? :)

R9295 commented 2 months ago

Good that I asked: https://pubs.opengroup.org/onlinepubs/9699919799/functions/readdir.html https://stackoverflow.com/questions/78185972/does-opendir-findfirstfile-get-a-snapshot-of-a-directory

I'll add another check

R9295 commented 2 months ago

A suggestion for fuzzer resumes: the coverage worker can check the fuzzer_stats file of the main afl node, find it's last update and continue with entries created from that point (if there is no need to reset coverage)