Skip to content

A few more small fuzzing fixes - #2770

Merged
alexcrichton merged 3 commits into
bytecodealliance:mainfrom
alexcrichton:more-fuzz-fixes-again
Mar 25, 2021
Merged

A few more small fuzzing fixes#2770
alexcrichton merged 3 commits into
bytecodealliance:mainfrom
alexcrichton:more-fuzz-fixes-again

Conversation

@alexcrichton

Copy link
Copy Markdown
Member

I found a few more things going through more fuzz failures, and after this I think I'll wait for oss-fuzz to ingest this batch of changes before tackling the remaining fuzz bugs.

The wasm-smith limits for generating modules are a bit higher than what
we specify, so sync those up to avoid getting too many false positives
with limits getting blown.
I keep looking at `*.wat` files that are actually stale, so remove stale
files if we write out a `*.wasm` file and can't disassemble it.
Fixes an issues where the same name is imported twice and we generated
two values for that. We don't mind the error here, we just want to
ignore the shadowing errors.
@github-actions github-actions Bot added the fuzzing Issues related to our fuzzing infrastructure label Mar 25, 2021
@github-actions

Copy link
Copy Markdown

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 .github/subscribe-to-label.json configuration file.

Learn more.

@alexcrichton
alexcrichton merged commit 516a97b into bytecodealliance:main Mar 25, 2021
@alexcrichton
alexcrichton deleted the more-fuzz-fixes-again branch March 25, 2021 23:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

fuzzing Issues related to our fuzzing infrastructure

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants