refactor(ll): adapt the fuse-abi
crate
#290
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi there,
I have published the
fuse-abi
crate for autogenerated, up-to-date bindings to FUSE devices, which is also usable inno_std
environments such as OS kernels.This initial unclean port of
fuser
tofuse-abi
seems to work in practice, according to CI.The most important difference to
fuser::ll::fuse_abi
is that the crate's struct's fields are not feature-gated. This would requirefuser
to adapt another approach to access to versioned fields which change the struct's size. This does not happen a lot, but there are cases such as withfuse_mknod_in
, which libfuse handles like this.If you are open to such an approach or have another idea to this issue, I'd be happy to continue working on this. I just wanted to test the waters before putting in more work. :)