test: Add fuzzing to CI test + minor fix #71
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
Issue: afl-gcc has been deprecated in v4.30 afl-cc doesn't understand some lwip comile flags afl-gcc-fast cannot be used to generate deps Fix: Use afl-gcc-fast for compilation, afl-cc for deps Note: Could use standard gcc for deps generation
Running it for 10 minutes is a good tradeoff to check for regression and not waste too much of CI resources
david-cermak
force-pushed
the
fix/fuzz_updates
branch
from
e1df1ba to
5aa218f
Compare
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.
This PR fixes recently deprecated afl-gcc in AFL 4.30c. Uses gcc for dependency generation, and afl-gcc-fast for compilation.
It also adds the initial lwip_fuzz target to CI, running for for 10 minutes, saving potential crashes to artifacts.
Note that this fuzzing setup is only testing simple, single-packet scenarios. The more advanced multi-packet (
lwip_fuzz2) and timing-aware (lwip_fuzz3) fuzzers are broken (or unfinished), disabled due to a input format mismatch. All our existing test inputs are raw Ethernet frames, while these advanced fuzzers expect structured inputs with length and timing metadata.I will address this in future PRs.