Caution: In this restricted "Fossies" environment the current HTML page may not be correctly presentated and may have some non-functional links.
Alternatively you can here view
the uninterpreted raw source code.
A member file download can also be achieved by clicking within a package contents listing on the according byte size field.
Directory entry parameters supplied to fuse_reply_entry()
Definition at line 59 of file fuse_lowlevel.h.
|struct stat fuse_entry_param::attr
Even if attr_timeout == 0, attr must be correct. For example, for open(), FUSE uses attr.st_size from lookup() to determine how many bytes to request. If this value is not correct, incorrect data will be returned.
Definition at line 91 of file fuse_lowlevel.h.
Validity timeout (in seconds) for inode attributes. If attributes only change as a result of requests that come through the kernel, this should be set to a very large value.
Definition at line 97 of file fuse_lowlevel.h.
Validity timeout (in seconds) for the name. If directory entries are changed/deleted only as a result of requests that come through the kernel, this should be set to a very large value.
Definition at line 103 of file fuse_lowlevel.h.
Generation number for this entry.
If the file system will be exported over NFS, the ino/generation pairs need to be unique over the file system's lifetime (rather than just the mount time). So if the file system reuses an inode after it has been deleted, it must assign a new, previously unused generation number to the inode at the same time.
The generation must be non-zero, otherwise FUSE will treat it as an error.
Definition at line 82 of file fuse_lowlevel.h.
Unique inode number
In lookup, zero means negative entry (from version 2.5) Returning ENOENT also means negative entry, but by setting zero ino the kernel may cache negative entries for entry_timeout seconds.
Definition at line 67 of file fuse_lowlevel.h.
The documentation for this struct was generated from the following file: