Work around a race condition where multiple AFL instances bind to the same CPU #4
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…e multiple instances of AFL will lock onto the same CPU.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is the same issue @genewitch found and I can confirm it is also a problem on 64-core machines as well. The issue is that multiple instances of AFL will bind to the the same core. To see this in action:
head -n 25 $OUTPUT_DIR/$TARGET/*/afl-launch.log | grep binding | sort
I also did some experimentation and a 100 ms delay still resulted in two threads binding to CPU #0, but a 250 ms delay seems to reliably avoid any CPU contention.