Add optional handling of Nyx InvalidWriteToPayload event #2027
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 adds
AFL_NYX_HANDLE_INVALID_WRITE
to allow AFL++ to ignore the InvalidWriteToPayload event. If such events occur sporadically, it is most likely due to OOM in the guest where the kernel is reclaiming memory and therefore touching the payload buffer. I decided to count these as crashes, hoping that they remain visible with this approach (but with a zero-size log). However, this happens quite rarely in my local setup so it is difficult to test.Without this variable set, AFL++ will just die and leave qemu running in the background. Long term, we might want to change the default behavior here as well.