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

bind honggfuzz to CPUs? #35

Open
vanhauser-thc opened this issue Aug 10, 2023 · 1 comment
Open

bind honggfuzz to CPUs? #35

vanhauser-thc opened this issue Aug 10, 2023 · 1 comment

Comments

@vanhauser-thc
Copy link
Collaborator

honggfuzz allows for binding to a CPU with --pin_thread_cpu=1
however it is very ineffective/naive about this, it always binds the same CPUs, even if multiple honggfuzz fuzzing campaigns are running.
As long as not more than 2 fuzzing campaigns are running, this options would be beneficial to have. (because of all the locking honggfuzz cannot achieve 100% load on a thread like afl++). but with 3+ campaign this would make fuzzing with honggfuzz worse.
maybe lets have this as an option, default on?

also important is for that not to impact AFL++, first honggfuzz has to be started and then afl-fuzz, as afl-fuzz binds to unused CPUs (and honggfuzz doesnt care).

@louismerlin
Copy link
Collaborator

Implemented in https://github.com/srlabs/ziggy/tree/fuzzing-improvements.

I'll also implement #33 there soon and include both in an upcoming release.

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