Stream: git-wasmtime

Topic: wasmtime / issue #3836 `wasm-mutate` fuzz targets

view this post on Zulip Wasmtime GitHub notifications bot (Feb 22 2022 at 22:06):

github-actions[bot] commented on issue #3836:

Subscribe to Label Action

cc @fitzgen

<details>
This issue or pull request has been labeled: "fuzzing"

Thus the following users have been cc'd because of the following labels:

To subscribe or unsubscribe from this label, edit the <code>.github/subscribe-to-label.json</code> configuration file.

Learn more.
</details>

view this post on Zulip Wasmtime GitHub notifications bot (Feb 23 2022 at 19:30):

fitzgen commented on issue #3836:

Could this be installed directly into the compile target as a mutator or do we need a second target for this?

I just wanted to be conservative about rolling this out. Also, I don't think it is a bad thing to have multiple mutators at work here. wasm-mutate is far from complete, so keeping the raw libfuzzer mutator around is good.

Depending on the coverage from this I think it would be great to hook into the "actually run code" fuzz targets at some point but that's fine to do later.

Yep, agreed.

For a corpus, could we just run wasm-smith on a bunch of inputs, throw all the outputs in a directory, and then shrink it based on coverage?

Yeah, probably good to add the sightglass benchmarks and any other Wasm binaries we have lying around too. More is better! Can always shrink the corpus after the fact.

Last updated: Nov 22 2024 at 16:03 UTC