f4d3f08fc6
* Fix path_get returning ENOTDIR when base not dir This commit makes certain adjustments to `WasiCtx` and `FdEntry` by introducing methods `get_nonvalidated_fd_entry` and `get_nonvalidated_fd_entry_mut` which only check if the `FdEntry` corresponding to the specified raw WASI fd exists in the context object but **without** automatically validating the rights. Thanks to postponing the validation until after the `FdEntry` object is extracted from the context, it is possible to check if the extracted `FdEntry` object is indeed a valid dir descriptor when processing paths in `path_get` helper fn. In essence then, this commit closes #158. * Remove potentially useless FdObject struct This commit removes `FdObject` struct which wasn't really used in our codebase, and flattens its contents into `FdEntry`. IMHO, this cleans up a fair amount of code and generally unclutters it. * Refactor and document `WasiCtx` and `FdEntry` This commit refactors `WasiCtx` struct by making the collection of `FdEntry`s stored within private, and only allowing it to be accessed via the provided set of modifier methods (push, insert, remove, etc.). Additionally, this commit documents the methods of `WasiCtx` and `FdEntry` structs for easier debugging and maintenance in the future.
wasi-common
This repo will ultimately serve as a library providing a common implementation of WASI hostcalls for re-use in any WASI (and potentially non-WASI) runtimes such as Wasmtime and Lucet.
The library is an adaption of lucet-wasi crate from the Lucet project, and it is currently based on 40ae1df git revision.
Please note that the library requires Rust compiler version at least 1.37.0.
Supported syscalls
*nix
In our *nix implementation, we currently support the entire WASI API with the exception of socket hostcalls:
sock_recvsock_sendsock_shutdown
We expect these to be implemented when network access is standardised.
We also currently do not support the proc_raise hostcall, as it is expected to
be dropped entirely from WASI.
Windows
In our Windows implementation, we currently support the minimal subset of WASI API which allows for running the very basic "Hello world!" style WASM apps. More coming shortly, so stay tuned!
Development hints
When testing the crate, you may want to enable and run full wasm32 integration testsuite. This
requires wasm32-wasi target installed which can be done as follows using rustup
rustup target add wasm32-wasi
Next initiate submodules containing the integration testsuite
git submodule update --init
Now, you should be able to run the integration testsuite by enabling the wasm_tests feature
cargo test --features wasm_tests
Third-Party Code
Significant parts of our hostcall implementations are derived from the C implementations in
cloudabi-utils. See LICENSE.cloudabi-utils for license information.