Enum fidl_fuchsia_io::Directory2Request

pub enum Directory2Request {
    Close {
        responder: Directory2CloseResponder,
    },
    Query {
        responder: Directory2QueryResponder,
    },
    Reopen {
        rights_request: Option<Box<RightsRequest>>,
        object_request: ServerEnd<NodeMarker>,
        control_handle: Directory2ControlHandle,
    },
    GetConnectionInfo {
        responder: Directory2GetConnectionInfoResponder,
    },
    GetAttributes {
        query: NodeAttributesQuery,
        responder: Directory2GetAttributesResponder,
    },
    UpdateAttributes {
        payload: MutableNodeAttributes,
        responder: Directory2UpdateAttributesResponder,
    },
    Sync {
        responder: Directory2SyncResponder,
    },
    AdvisoryLock {
        request: AdvisoryLockRequest,
        responder: Directory2AdvisoryLockResponder,
    },
    Open2 {
        path: String,
        protocols: ConnectionProtocols,
        object_request: Channel,
        control_handle: Directory2ControlHandle,
    },
    AddInotifyFilter {
        path: String,
        filter: InotifyWatchMask,
        watch_descriptor: u32,
        socket: Socket,
        responder: Directory2AddInotifyFilterResponder,
    },
    Unlink {
        name: String,
        options: UnlinkOptions,
        responder: Directory2UnlinkResponder,
    },
    Enumerate {
        options: DirectoryEnumerateOptions,
        iterator: ServerEnd<DirectoryIteratorMarker>,
        control_handle: Directory2ControlHandle,
    },
    Rename {
        src: String,
        dst_parent_token: Event,
        dst: String,
        responder: Directory2RenameResponder,
    },
}

A [Node2] that is capable of containing other nodes.

Variants

Close

Fields

responder: Directory2CloseResponder

Terminates the connection.

After calling Close, the client must not send any other requests.

Servers, after sending the status response, should close the connection regardless of status and without sending an epitaph.

Closing the client end of the channel should be semantically equivalent to calling Close without knowing when the close has completed or its status.

Query

Fields

responder: Directory2QueryResponder

Reopen

Fields

rights_request: Option<Box<RightsRequest>>

object_request: ServerEnd<NodeMarker>

control_handle: Directory2ControlHandle

Creates another connection to the same node.

• object_request is the server end of a channel created for the new connection. The caller may proceed to send messages on the corresponding client end right away.

GetConnectionInfo

Fields

responder: Directory2GetConnectionInfoResponder

Acquires information about the connection.

This method does not require any rights.

GetAttributes

Fields

query: NodeAttributesQuery

responder: Directory2GetAttributesResponder

Acquires information about the node.

The attributes of a node should be stable, independent of the specific protocol used to access it.

If a particular attribute is not applicable or not supported, filesystems should leave the corresponding field absent.

• query a bit-mask specifying which attributes to fetch. The server should not return more than necessary.

• attributes the returned attributes.

This method requires the [Rights.GET_ATTRIBUTES] right.

UpdateAttributes

Fields

payload: MutableNodeAttributes

responder: Directory2UpdateAttributesResponder

Updates information about the node.

• attributes the presence of a table field in attributes indicates the intent to update the corresponding attribute.

This method requires the [Rights.UPDATE_ATTRIBUTES] right.

Sync

Fields

responder: Directory2SyncResponder

Synchronizes updates to the node to the underlying media, if it exists.

This method will return when the filesystem server has flushed the relevant updates to the underlying media, but does not guarantee the underlying media has persisted the information, nor that any information is committed to hardware. Clients may use Sync to ensure ordering between operations.

This method does not require any rights.

AdvisoryLock

Fields

request: AdvisoryLockRequest

responder: Directory2AdvisoryLockResponder

Acquires an advisory lock on the underlying file.

The lock lasts until either this connection is closed or this method is called with |AdvisoryLockType.UNLOCK| to release the lock explicitly.

Advisory locks are purely advisory. They do not prevent actual read or write operations from occurring on the file, either through this connection or through other connections.

This method requires the following rights:

• [Rights.READ_BYTES] if request.type is [AdvisoryLockType.READ].
• [Rights.WRITE_BYTES] if request.type is [AdvisoryLockType.WRITE].

Errors

• ZX_ERR_BAD_STATE The specified type of lock cannot be acquired. For example, another connection might hold a conflicting lock type.
• ZX_ERR_NOT_SUPPORTED This file does not support advisory locking.
• ZX_ERR_ACCESS_DENIED This connection does not have sufficient rights to acquire the given type of lock.

Open2

Fields

path: String

protocols: ConnectionProtocols

object_request: Channel

control_handle: Directory2ControlHandle

Opens or creates a new node relative to this directory node.

This method requires the following rights on the current connection:

• [Rights.ENUMERATE]
• [Rights.TRAVERSE]

Errors are presented as an epitaph on the object_request channel.

• error ZX_ERR_ACCESS_DENIED if the requested rights exceeds what is allowed.
• error ZX_ERR_BAD_PATH if path is invalid.

AddInotifyFilter

Fields

path: String

filter: InotifyWatchMask

watch_descriptor: u32

socket: Socket

responder: Directory2AddInotifyFilterResponder

Adds a new inotify filter for an object relative to this directory object.

• ’filter` is a mask of different inotify events that need to be watched by the server for a specific file/directory.

• path may contain multiple segments, separated by “/” characters, and should never be empty; i.e., “” is an invalid path. Paths should not contain a leading “/”.

+watch_descriptor is client assigned value to identify a filter. Server shouldn’t trust the client-assigned watch_descriptor. They should just send it back to the client in the socket. This value is not used by server, but it is returned back as part of InotifyEvent, to help the client correlate filter with events on this filter.

• socket is shared between different filter objects i.e every new filter will have a different server end of the socket and there will be a single client end per inotify instance on inotify init.

Unlink

Fields

name: String

options: UnlinkOptions

responder: Directory2UnlinkResponder

Removes a child node from the this directory’s list of entries.

Note: this does not guarantee that the underlying object is destroyed. Although the link will be removed from the containing directory, objects with multiple references (such as files which are still open) will not actually be destroyed until all references are closed.

• error ZX_ERR_ACCESS_DENIED if the connection does not have [Rights.WRITE_BYTES].
• error ZX_ERR_NOT_SUPPORTED if the underlying filesystem does not support writing.
• error ZX_ERR_BAD_PATH if name is invalid.
• error ZX_ERR_NOT_EMPTY if name refers to a non-empty directory.
• error ZX_ERR_UNAVAILABLE if name refers to a mount point, containing a remote channel.
• error ZX_ERR_NOT_DIR if the options requested a directory but something other than a directory was found.

Other errors may be returned for filesystem-specific reasons.

This method requires the following rights:

• [Rights.ENUMERATE]
• [Rights.MODIFY_DIRECTORY]

Enumerate

Fields

options: DirectoryEnumerateOptions

iterator: ServerEnd<DirectoryIteratorMarker>

control_handle: Directory2ControlHandle

Initiates a directory listing operation over the input channel, starting at seek offset 0.

This method requires the [Rights.ENUMERATE] right. If this right is absent, iterator will be closed with a ZX_ERR_ACCESS_DENIED epitaph.

Rename

Fields

src: String

dst_parent_token: Event

dst: String

responder: Directory2RenameResponder

Renames a node named src to the name dst, in a directory represented by dst_parent_token.

src and dst must be valid node names. See [Name] for what constitutes a valid name.

This method requires the following rights on both the current connection, and the connection identified by dst_parent_token:

• [Rights.ENUMERATE]

• [Rights.MODIFY_DIRECTORY]

• error ZX_ERR_INVALID_ARGS if src or dst is invalid.

Implementations

impl Directory2Request

pub fn into_close(self) -> Option<Directory2CloseResponder>

pub fn into_query(self) -> Option<Directory2QueryResponder>

pub fn into_reopen( self ) -> Option<(Option<Box<RightsRequest>>, ServerEnd<NodeMarker>, Directory2ControlHandle)>

pub fn into_get_connection_info( self ) -> Option<Directory2GetConnectionInfoResponder>

pub fn into_get_attributes( self ) -> Option<(NodeAttributesQuery, Directory2GetAttributesResponder)>

pub fn into_update_attributes( self ) -> Option<(MutableNodeAttributes, Directory2UpdateAttributesResponder)>

pub fn into_sync(self) -> Option<Directory2SyncResponder>

pub fn into_advisory_lock( self ) -> Option<(AdvisoryLockRequest, Directory2AdvisoryLockResponder)>

pub fn into_open2( self ) -> Option<(String, ConnectionProtocols, Channel, Directory2ControlHandle)>

pub fn into_add_inotify_filter( self ) -> Option<(String, InotifyWatchMask, u32, Socket, Directory2AddInotifyFilterResponder)>

pub fn into_unlink( self ) -> Option<(String, UnlinkOptions, Directory2UnlinkResponder)>

pub fn into_enumerate( self ) -> Option<(DirectoryEnumerateOptions, ServerEnd<DirectoryIteratorMarker>, Directory2ControlHandle)>

pub fn into_rename( self ) -> Option<(String, Event, String, Directory2RenameResponder)>

pub fn method_name(&self) -> &'static str

Name of the method defined in FIDL

Trait Implementations

impl Debug for Directory2Request

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.