vhost_user: handle recv_with_fds being unsafe #69
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.
recv_with_fds
from vmm-sys-util was never safe, but was incorrectly not marked as safe. Handle it safely in every function where we have enough information to know that calling it will be safe, and propogate the unsafe to any function where we don't.Fortunately this is quite straightforward now all of the high-level methods have the guarantee that they're returning
ByteValued
types.Signed-off-by: Alyssa Ross hi@alyssa.is
This change is necessitated by rust-vmm/vmm-sys-util#135. If it's merged before the vmm-sys-util dependency is updated to a version with that change, it will produce compiler warnings, so I've marked it as a draft until that PR is merged.