Lines Matching defs:flush
260 * for the purpose of checking if auto_cache should flush the
269 * read, write, flush, release, fallocate, fsync, readdir,
311 * filesystem (e.g. getattr). Open, flush, release, fsync, opendir,
445 * operations (read, write, flush, release, fsync).
493 /** Possibly flush cached data
500 * a file. Under Linux, errors returned by flush() will be passed to
501 * userspace as errors from close(), so flush() is a good place to write
503 * on close(), and on non-Linux systems, close() may succeed even if flush()
505 * that errors returned by flush will ever be noticed or even
508 * NOTE: The flush() method may be called more than once for each
511 * not possible to determine if a flush is final, so each flush should
512 * be treated equally. Multiple write-flush sequences are relatively
515 * Filesystems shouldn't assume that flush will be called at any
521 int (*flush) (const char *, struct fuse_file_info *);