Flag another error as ok to hit when fuzzing (#3092)
We've got a lot of fuzz failures right now of modules instantiating memories of 65536 pages, which we specifically disallow since the representation of limits within Wasmtime don't support full 4GB memories. This is ok, however, and it's not a fuzz failure that we're interested in, so this commit allows strings of that error to pass through the fuzzer.
This commit is contained in:
@@ -172,6 +172,9 @@ pub fn instantiate_with_config(
|
||||
// every single module under the sun due to using name-based resolution
|
||||
// rather than positional-based resolution
|
||||
|| string.contains("incompatible import type")
|
||||
// If we ran out of resources instantiating this wasm module that's
|
||||
// ok, no need to consider that a fatal error.
|
||||
|| string.contains("Insufficient resources")
|
||||
{
|
||||
return;
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user