VmoBackedServerTestingExt

vmo_backed_block_server

Trait VmoBackedServerTestingExt 

Source 
pub trait VmoBackedServerTestingExt {
    // Required methods
    fn new(block_count: u64, block_size: u32, initial_content: &[u8]) -> Self;
    fn from_vmo(block_size: u32, vmo: Vmo) -> Self;
    fn connect_server(self: &Arc<Self>, server: ServerEnd<BlockMarker>);
    fn connect<R: BlockClient>(self: &Arc<Self>) -> R;
    fn connect_insecure_inline_encryption_server(
        self: &Arc<Self>,
        server: ServerEnd<DeviceMarker>,
        uuid: [u8; 16],
    ) -> impl Future<Output = ()> + Send;
    fn evict_key_slot(&self, slot: u8) -> Result<(), Status>;
}
Expand description

Extension trait for test-only functionality. unwrap is used liberally in these functions, to simplify their usage in tests.

Required Methods§

Source

fn new(block_count: u64, block_size: u32, initial_content: &[u8]) -> Self

Source

fn from_vmo(block_size: u32, vmo: Vmo) -> Self

Source

fn connect_server(self: &Arc<Self>, server: ServerEnd<BlockMarker>)

Source

fn connect<R: BlockClient>(self: &Arc<Self>) -> R

Source

fn connect_insecure_inline_encryption_server( self: &Arc<Self>, server: ServerEnd<DeviceMarker>, uuid: [u8; 16], ) -> impl Future<Output = ()> + Send

Source

fn evict_key_slot(&self, slot: u8) -> Result<(), Status>

Evicts the key slots from fscrypt_keys.

Dyn Compatibility§

This trait is not dyn compatible.

In older versions of Rust, dyn compatibility was called "object safety", so this trait is not object safe.

Implementors§