|unsigned int||writepage: 1|
|unsigned int||direct_io: 1|
|unsigned int||keep_cache: 1|
|unsigned int||flush: 1|
|unsigned int||nonseekable: 1|
|unsigned int||cache_readdir: 1|
|unsigned int||padding: 25|
Information about an open file.
File Handles are created by the open, opendir, and create methods and closed by the release and releasedir methods. Multiple file handles may be concurrently open for the same file. Generally, a client will create one file handle per file descriptor, though in some cases multiple file descriptors can share a single file handle.
|unsigned int fuse_file_info::cache_readdir|
|unsigned int fuse_file_info::direct_io|
|unsigned int fuse_file_info::flush|
|unsigned int fuse_file_info::keep_cache|
Can be filled in by open. It signals the kernel that any currently cached file data (ie., data that the filesystem provided the last time the file was open) need not be invalidated. Has no effect when set in other contexts (in particular it does nothing when set by opendir()).
|unsigned int fuse_file_info::nonseekable|
|unsigned int fuse_file_info::padding|
|unsigned int fuse_file_info::writepage|
In case of a write operation indicates if this was caused by a delayed write from the page cache. If so, then the context's pid, uid, and gid fields will not be valid, and the fh value may not match the fh value that would have been sent with the corresponding individual write requests if write caching had been disabled.