Add fuzz coverage for SV1 JSON-RPC messages#2163
Open
0xjc65eth wants to merge 1 commit into
Open
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
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.
Summary
deserialize_sv1_json_rpcto fuzz arbitrary SV1 JSON-RPC bytes through serde and method parsingroundtrip_sv1_messagesto generate representative SV1 client/server messages and round-trip them through JSON-RPC parsingsv1_apicrate into the existing fuzz manifestCloses #2124.
Testing
cargo +1.89.0 check --manifest-path fuzz/Cargo.toml --bin deserialize_sv1_json_rpc --bin roundtrip_sv1_messagescargo +nightly fuzz run deserialize_sv1_json_rpc -- -max_total_time=5cargo +nightly fuzz run roundtrip_sv1_messages -- -max_total_time=5late bytes still tell the truth.