linux/fs/fuse, branch v3.15.3

fuse: add renameat2 support

2014-04-28T14:43:44Z

Support RENAME_EXCHANGE and RENAME_NOREPLACE flags on the userspace ABI. Signed-off-by: Miklos Szeredi

fuse: clear MS_I_VERSION

2014-04-28T12:19:25Z

Fuse doesn't support i_version (yet). Signed-off-by: Miklos Szeredi

fuse: clear FUSE_I_CTIME_DIRTY flag on setattr

2014-04-28T12:19:25Z

The patch addresses two use-cases when the flag may be safely cleared: 1. fuse_do_setattr() is called with ATTR_CTIME flag set in attr->ia_valid. In this case attr->ia_ctime bears actual value. In-kernel fuse must send it to the userspace server and then assign the value to inode->i_ctime. 2. fuse_do_setattr() is called with ATTR_SIZE flag set in attr->ia_valid, whereas ATTR_CTIME is not set (truncate(2)). In this case in-kernel fuse must sent "now" to the userspace server and then assign the value to inode->i_ctime. In both cases we could clear I_DIRTY_SYNC, but that needs more thought. Signed-off-by: Maxim Patlasov Signed-off-by: Miklos Szeredi

fuse: trust kernel i_ctime only

2014-04-28T12:19:24Z

Let the kernel maintain i_ctime locally: update i_ctime explicitly on truncate, fallocate, open(O_TRUNC), setxattr, removexattr, link, rename, unlink. The inode flag I_DIRTY_SYNC serves as indication that local i_ctime should be flushed to the server eventually. The patch sets the flag and updates i_ctime in course of operations listed above. Signed-off-by: Maxim Patlasov Signed-off-by: Miklos Szeredi

fuse: remove .update_time

2014-04-28T12:19:24Z

This implements updating ctime as well as mtime on file_update_time(). Signed-off-by: Miklos Szeredi

fuse: allow ctime flushing to userspace

2014-04-28T12:19:24Z

The patch extends fuse_setattr_in, and extends the flush procedure (fuse_flush_times()) called on ->write_inode() to send the ctime as well as mtime. Signed-off-by: Maxim Patlasov Signed-off-by: Miklos Szeredi

fuse: fuse: add time_gran to INIT_OUT

2014-04-28T12:19:23Z

Allow userspace fs to specify time granularity. This is needed because with writeback_cache mode the kernel is responsible for generating mtime and ctime, but if the underlying filesystem doesn't support nanosecond granularity then the cache will contain a different value from the one stored on the filesystem resulting in a change of times after a cache flush. Make the default granularity 1s. Signed-off-by: Miklos Szeredi

fuse: add .write_inode

2014-04-28T12:19:23Z

...and flush mtime from this. This allows us to use the kernel infrastructure for writing out dirty metadata (mtime at this point, but ctime in the next patches and also maybe atime). Signed-off-by: Miklos Szeredi

fuse: clean up fsync

2014-04-28T12:19:23Z

Don't need to start I/O twice (once without i_mutex and one within). Also make sure that even if the userspace filesystem doesn't support FSYNC we do all the steps other than sending the message. Signed-off-by: Miklos Szeredi

fuse: fuse: fallocate: use file_update_time()

2014-04-28T12:19:22Z

in preparation for getting rid of FUSE_I_MTIME_DIRTY. Signed-off-by: Miklos Szeredi