Stream: git-wasmtime

Topic: wasmtime / issue #4626 aarch64: assertion failed: (end_of...

Wasmtime GitHub notifications bot (Aug 05 2022 at 21:52):

alexcrichton opened issue #4626:

Given this input wasm:

$ export CARGO_PROFILE_RELEASE_DEBUG_ASSERTIONS=true
$ cargo run --release --features all-arch compile adapter.wasm --wasm-features all
    Finished release [optimized] target(s) in 0.15s
     Running `target/release/wasmtime compile adapter.wasm --wasm-features all`
thread '<unnamed>' panicked at 'assertion failed: (end_off - start_off) <= Inst::worst_case_size()', cranelift/codegen/src/isa/aarch64/inst/emit.rs:3140:9
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

This was found via a generated adapter module that is part of the component_api fuzzer. The adapter itself is probably copying over a massively deep type we could place limits on elsewhere, but as an arbitrary input to a core wasm module this should probably also not panic the backend.

Wasmtime GitHub notifications bot (Aug 05 2022 at 21:52):

alexcrichton labeled issue #4626:

Given this input wasm:

$ export CARGO_PROFILE_RELEASE_DEBUG_ASSERTIONS=true
$ cargo run --release --features all-arch compile adapter.wasm --wasm-features all
    Finished release [optimized] target(s) in 0.15s
     Running `target/release/wasmtime compile adapter.wasm --wasm-features all`
thread '<unnamed>' panicked at 'assertion failed: (end_off - start_off) <= Inst::worst_case_size()', cranelift/codegen/src/isa/aarch64/inst/emit.rs:3140:9
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

This was found via a generated adapter module that is part of the component_api fuzzer. The adapter itself is probably copying over a massively deep type we could place limits on elsewhere, but as an arbitrary input to a core wasm module this should probably also not panic the backend.

Wasmtime GitHub notifications bot (Aug 06 2022 at 00:27):

cfallin closed issue #4626:

Given this input wasm:

$ export CARGO_PROFILE_RELEASE_DEBUG_ASSERTIONS=true
$ cargo run --release --features all-arch compile adapter.wasm --wasm-features all
    Finished release [optimized] target(s) in 0.15s
     Running `target/release/wasmtime compile adapter.wasm --wasm-features all`
thread '<unnamed>' panicked at 'assertion failed: (end_off - start_off) <= Inst::worst_case_size()', cranelift/codegen/src/isa/aarch64/inst/emit.rs:3140:9
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

This was found via a generated adapter module that is part of the component_api fuzzer. The adapter itself is probably copying over a massively deep type we could place limits on elsewhere, but as an arbitrary input to a core wasm module this should probably also not panic the backend.

Last updated: Nov 22 2024 at 17:03 UTC