workloads/lnd: map coverage counters directly onto AFL's map - #261
Open
erickcestari wants to merge 1 commit into
Open
erickcestari wants to merge 1 commit into
erickcestari wants to merge 1 commit into
Conversation
Remap Go's libfuzzer counter section onto the AFL shared memory instead of copying it on every sync. Startup coverage no longer pollutes every map, and crashing or timed-out inputs now report coverage. The trigger/ack pipes stay as a liveness handshake: try_wait still sees a just-crashed LND as running.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Remap Go's libfuzzer counter section onto the AFL shared memory instead of copying it on every sync. Startup coverage no longer pollutes every map, and crashing or timed-out inputs now report coverage.
The trigger/ack pipes stay as a liveness handshake: try_wait still sees a just-crashed LND as running.
I didn't yet run an evaluation to see the coverage increasing, but this should align the coverage report with the others implementation. Where the startup coverage don't pollute every map, since each input will be started from a zeroed map.