Stream: git-wasmtime

Topic: wasmtime / issue #4818 Update `wasmi` differential fuzzing

Wasmtime GitHub notifications bot (Aug 30 2022 at 09:44):

Robbepop opened issue #4818:

Wasmtime has implemented differential fuzzing against the wasmi interpreter. However, the currently supported wasmi version is very old and outdated.

Benefits

The wasmi interpreter has since evolved quite a lot and could be helpful to more extensively fuzzy test against Wasmtime's feature set.

• Fuzz test against modern wasmi versions instead of ancient one.
• Being able to fuzz test against some Wasm proposals whereas the old wasmi only supported Wasm MVP.
• Higher fuzz testing throughput since the newer wasmi versions are a lot faster.
• New wasmi versions offer an API similar to the API of Wasmtime, therefore fuzz testing code should become slightly cleaner.

Downsides

The biggest downside is that the newer wasmi versions are not as battle tested as the old ones and therefore we might risk some false positives on the wasmi side which could introduce noise.

Implementation

I would open a PR myself if this issue is accepted. Shouldn't be too hard to update.

Alternatives

Stay on the current old wasmi version since it is quite stable and battle tested.

Wasmtime GitHub notifications bot (Aug 30 2022 at 14:28):

alexcrichton commented on issue #4818:

Updating would be great! If you'd like to send a PR I'd be happy to review. If you've got ideas about how to improve the differential fuzzing interface feel free to throw those in as well!

Wasmtime GitHub notifications bot (Aug 30 2022 at 14:28):

alexcrichton labeled issue #4818:

Wasmtime has implemented differential fuzzing against the wasmi interpreter. However, the currently supported wasmi version is very old and outdated.

Benefits

The wasmi interpreter has since evolved quite a lot and could be helpful to more extensively fuzzy test against Wasmtime's feature set.

• Fuzz test against modern wasmi versions instead of ancient one.
• Being able to fuzz test against some Wasm proposals whereas the old wasmi only supported Wasm MVP.
• Higher fuzz testing throughput since the newer wasmi versions are a lot faster.
• New wasmi versions offer an API similar to the API of Wasmtime, therefore fuzz testing code should become slightly cleaner.

Downsides

The biggest downside is that the newer wasmi versions are not as battle tested as the old ones and therefore we might risk some false positives on the wasmi side which could introduce noise.

Implementation

I would open a PR myself if this issue is accepted. Shouldn't be too hard to update.

Alternatives

Stay on the current old wasmi version since it is quite stable and battle tested.

Wasmtime GitHub notifications bot (Aug 30 2022 at 14:29):

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

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:

• fitzgen: fuzzing

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

Learn more.
</details>

Wasmtime GitHub notifications bot (Aug 30 2022 at 15:10):

Robbepop commented on issue #4818:

>

Cool, I will come up with a PR in the next days. I have not yet taken an in-depth look at the Wasmtime fuzzing interface but will do when I am working on it and maybe come up with improvements. :)

Wasmtime GitHub notifications bot (Aug 30 2022 at 15:10):

Robbepop edited a comment on issue #4818:

Updating would be great! If you'd like to send a PR I'd be happy to review. If you've got ideas about how to improve the differential fuzzing interface feel free to throw those in as well!

Cool, I will come up with a PR in the next days. I have not yet taken an in-depth look at the Wasmtime fuzzing interface but will do when I am working on it and maybe come up with improvements. :)

Wasmtime GitHub notifications bot (Oct 24 2022 at 16:41):

alexcrichton closed issue #4818:

Wasmtime has implemented differential fuzzing against the wasmi interpreter. However, the currently supported wasmi version is very old and outdated.

Benefits

The wasmi interpreter has since evolved quite a lot and could be helpful to more extensively fuzzy test against Wasmtime's feature set.

• Fuzz test against modern wasmi versions instead of ancient one.
• Being able to fuzz test against some Wasm proposals whereas the old wasmi only supported Wasm MVP.
• Higher fuzz testing throughput since the newer wasmi versions are a lot faster.
• New wasmi versions offer an API similar to the API of Wasmtime, therefore fuzz testing code should become slightly cleaner.

Downsides

The biggest downside is that the newer wasmi versions are not as battle tested as the old ones and therefore we might risk some false positives on the wasmi side which could introduce noise.

Implementation

I would open a PR myself if this issue is accepted. Shouldn't be too hard to update.

Alternatives

Stay on the current old wasmi version since it is quite stable and battle tested.

Last updated: Dec 13 2025 at 15:03 UTC