rmm: Initial fuzzing setup #418
Open
Conversation
This file contains 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
Signed-off-by: Rayhan Faizel <[email protected]>
Signed-off-by: Rayhan Faizel <[email protected]>
Signed-off-by: Rayhan Faizel <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
(LFX Task 1)
This PR adds the initial fuzzing setup based on libfuzzer-sys along with two harnesses for RMI commands: FEATURES and VERSION.
Two scripts are provided:
./scripts/fuzz.sh <fuzzer_name> <var_args>- Runs the fuzzer. The script will run the fuzzer natively if the host is aarch64, otherwise it will fall back to QEMU userspace emulator../scripts/fuzz-coverage.sh <fuzzer_name> <duration>- Based on./scripts/code-coverage.sh, the fuzzer is run for a set duration and an html report is generated after at./code-coverage/index.html.