* directory. Optionally opendir may also return an arbitrary
* filehandle in the fuse_file_info structure, which will be
* passed to readdir, closedir and fsyncdir.
- *
- * Introduced in version 2.3
*/
int (*opendir) (const char *, struct fuse_file_info *);
* passes non-zero offset to the filler function. When the buffer
* is full (or an error happens) the filler function will return
* '1'.
- *
- * Introduced in version 2.3
- * The "flags" argument added in version 3.0
*/
int (*readdir) (const char *, void *, fuse_fill_dir_t, off_t,
struct fuse_file_info *, enum fuse_readdir_flags);
/** Release directory
- *
- * Introduced in version 2.3
*/
int (*releasedir) (const char *, struct fuse_file_info *);
*
* If the datasync parameter is non-zero, then only the user data
* should be flushed, not the meta data
- *
- * Introduced in version 2.3
*/
int (*fsyncdir) (const char *, int, struct fuse_file_info *);
* The return value will passed in the private_data field of
* fuse_context to all file operations and as a parameter to the
* destroy() method.
- *
- * Introduced in version 2.3
- * Changed in version 2.6
*/
void *(*init) (struct fuse_conn_info *conn);
* Clean up filesystem
*
* Called on filesystem exit.
- *
- * Introduced in version 2.3
*/
void (*destroy) (void *);
* called.
*
* This method is not called under Linux kernel versions 2.4.x
- *
- * Introduced in version 2.5
*/
int (*access) (const char *, int);
* If this method is not implemented or under Linux kernel
* versions earlier than 2.6.15, the mknod() and open() methods
* will be called instead.
- *
- * Introduced in version 2.5
*/
int (*create) (const char *, mode_t, struct fuse_file_info *);
* Note: if this method is not implemented, the kernel will still
* allow file locking to work locally. Hence it is only
* interesting for network filesystems and similar.
- *
- * Introduced in version 2.6
*/
int (*lock) (const char *, struct fuse_file_info *, int cmd,
struct flock *);
* *fi* will be NULL if the file is not currenly opened.
*
* See the utimensat(2) man page for details.
- *
- * Introduced in version 2.6
*/
int (*utimens) (const char *, const struct timespec tv[2],
struct fuse_file_info *fi);
*
* Note: This makes sense only for block device backed filesystems
* mounted with the 'blkdev' option
- *
- * Introduced in version 2.6
*/
int (*bmap) (const char *, size_t blocksize, uint64_t *idx);
*
* If flags has FUSE_IOCTL_DIR then the fuse_file_info refers to a
* directory file handle.
- *
- * Introduced in version 2.8
*/
int (*ioctl) (const char *, int cmd, void *arg,
struct fuse_file_info *, unsigned int flags, void *data);
*
* The callee is responsible for destroying ph with
* fuse_pollhandle_destroy() when no longer in use.
- *
- * Introduced in version 2.8
*/
int (*poll) (const char *, struct fuse_file_info *,
struct fuse_pollhandle *ph, unsigned *reventsp);
* Similar to the write() method, but data is supplied in a
* generic buffer. Use fuse_buf_copy() to transfer data to
* the destination.
- *
- * Introduced in version 2.9
*/
int (*write_buf) (const char *, struct fuse_bufvec *buf, off_t off,
struct fuse_file_info *);
* location pointed to by bufp. If the buffer contains memory
* regions, they too must be allocated using malloc(). The
* allocated memory will be freed by the caller.
- *
- * Introduced in version 2.9
*/
int (*read_buf) (const char *, struct fuse_bufvec **bufp,
size_t size, off_t off, struct fuse_file_info *);
* Note: if this method is not implemented, the kernel will still
* allow file locking to work locally. Hence it is only
* interesting for network filesystems and similar.
- *
- * Introduced in version 2.9
*/
int (*flock) (const char *, struct fuse_file_info *, int op);
* file. If this function returns success then any subsequent write
* request to specified range is guaranteed not to fail because of lack
* of space on the file system media.
- *
- * Introduced in version 2.9.1
*/
int (*fallocate) (const char *, int, off_t, off_t,
struct fuse_file_info *);
/** Private filesystem data */
void *private_data;
- /** Umask of the calling process (introduced in version 2.8) */
+ /** Umask of the calling process */
mode_t umask;
};
writepage */
unsigned int writepage : 1;
- /** Can be filled in by open, to use direct I/O on this file.
- Introduced in version 2.4 */
+ /** Can be filled in by open, to use direct I/O on this file. */
unsigned int direct_io : 1;
/** Can be filled in by open, to indicate, that cached file data
- need not be invalidated. Introduced in version 2.4 */
+ need not be invalidated. */
unsigned int keep_cache : 1;
/** Indicates a flush operation. Set in flush operation, also
maybe set in highlevel lock operation and lowlevel release
- operation. Introduced in version 2.6 */
+ operation. */
unsigned int flush : 1;
/** Can be filled in by open, to indicate that the file is not
- seekable. Introduced in version 2.8 */
+ seekable. */
unsigned int nonseekable : 1;
/* Indicates that flock locks for this file should be
released. If set, lock_owner shall contain a valid value.
- May only be set in ->release(). Introduced in version
- 2.9 */
+ May only be set in ->release(). */
unsigned int flock_release : 1;
/** Padding. Do not use*/
uint64_t lock_owner;
/** Requested poll events. Available in ->poll. Only set on kernels
- which support it. If unsupported, this field is set to zero.
- Introduced in version 3.0 */
+ which support it. If unsupported, this field is set to zero. */
uint32_t poll_events;
};
*
* This method is not called under Linux kernel versions 2.4.x
*
- * Introduced in version 2.5
- *
* Valid replies:
* fuse_reply_err
*
* versions earlier than 2.6.15, the mknod() and open() methods
* will be called instead.
*
- * Introduced in version 2.5
- *
* Valid replies:
* fuse_reply_create
* fuse_reply_err
/**
* Test for a POSIX file lock
*
- * Introduced in version 2.6
- *
* Valid replies:
* fuse_reply_lock
* fuse_reply_err
* will still allow file locking to work locally. Hence these are
* only interesting for network filesystems and similar.
*
- * Introduced in version 2.6
- *
* Valid replies:
* fuse_reply_err
*
* Note: This makes sense only for block device backed filesystems
* mounted with the 'blkdev' option
*
- * Introduced in version 2.6
- *
* Valid replies:
* fuse_reply_bmap
* fuse_reply_err
* restricted ioctls, kernel prepares in/out data area
* according to the information encoded in cmd.
*
- * Introduced in version 2.8
- *
* Valid replies:
* fuse_reply_ioctl_retry
* fuse_reply_ioctl
/**
* Poll for IO readiness
*
- * Introduced in version 2.8
- *
* Note: If ph is non-NULL, the client should notify
* when IO readiness events occur by calling
* fuse_lowelevel_notify_poll() with the specified ph.
* bufv->off is correctly updated (reflecting the number of
* bytes read from bufv->buf[0]).
*
- * Introduced in version 2.9
- *
* Valid replies:
* fuse_reply_write
* fuse_reply_err
/**
* Callback function for the retrieve request
*
- * Introduced in version 2.9
- *
* Valid replies:
* fuse_reply_none
*
* See description of the forget function for more
* information.
*
- * Introduced in version 2.9
- *
* Valid replies:
* fuse_reply_none
*
* will still allow file locking to work locally. Hence these are
* only interesting for network filesystems and similar.
*
- * Introduced in version 2.9
- *
* Valid replies:
* fuse_reply_err
*
* subsequent writes to the specified range shall not fail due to the lack
* of free space on the file system storage media.
*
- * Introduced in version 2.9
- *
* Valid replies:
* fuse_reply_err
*
* the lookup count of every entry returned by readdirplus(), except "."
* and "..", is incremented by one.
*
- * Introduced in version 3.0
- *
* Valid replies:
* fuse_reply_buf
* fuse_reply_data
projects / qemu-gpiodev / libfuse.git / commitdiff