bind honggfuzz to CPUs?
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 87
- Forks
- 11
- Avg merge
- 11h 29m
- Merged PRs (30d)
- 2
Description
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).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Begin at handling for --pin_thread_cpu=1 and trace how ziggy launches honggfuzz and AFL++ campaigns. Define the desired CPU-allocation behavior for multiple campaigns and verify completion by testing two-campaign and 3+ campaign cases without regressing AFL++ coordination.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- devtools, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100