linux-toradex.git/fs/fuse, branch v4.1.2

VFS: normal filesystems (and lustre): d_inode() annotations

2015-04-15T19:06:57+00:00

that's the bulk of filesystem drivers dealing with inodes of their own

Signed-off-by: David Howells 
Signed-off-by: Al Viro

mirror O_APPEND and O_DIRECT into iocb->ki_flags

2015-04-12T02:30:22+00:00

... avoiding write_iter/fcntl races.

Signed-off-by: Al Viro

switch generic_write_checks() to iocb and iter

2015-04-12T02:30:21+00:00

... returning -E... upon error and amount of data left in iter after
(possible) truncation upon success.  Note, that normal case gives
a non-zero (positive) return value, so any tests for != 0 _must_ be
updated.

Signed-off-by: Al Viro 

Conflicts:
	fs/ext4/file.c

fuse: ->direct_IO() doesn't need generic_write_checks()

2015-04-12T02:29:50+00:00

already done by caller.  We used to call __fuse_direct_write(), which
called generic_write_checks(); now the former got expanded, bringing
the latter to the surface.  It used to be called all along and calling
it from there had been wrong all along...

Signed-off-by: Al Viro

generic_write_checks(): drop isblk argument

2015-04-12T02:29:48+00:00

all remaining callers are passing 0; some just obscure that fact.

Signed-off-by: Al Viro

direct_IO: remove rw from a_ops->direct_IO()

2015-04-12T02:29:45+00:00

Now that no one is using rw, remove it completely.

Signed-off-by: Omar Sandoval 
Signed-off-by: Al Viro

direct_IO: use iov_iter_rw() instead of rw everywhere

2015-04-12T02:29:45+00:00

The rw parameter to direct_IO is redundant with iov_iter->type, and
treated slightly differently just about everywhere it's used: some users
do rw & WRITE, and others do rw == WRITE where they should be doing a
bitwise check. Simplify this with the new iov_iter_rw() helper, which
always returns either READ or WRITE.

Signed-off-by: Omar Sandoval 
Signed-off-by: Al Viro

fuse: use iov_iter_get_pages() for non-splice path

2015-04-12T02:29:41+00:00

store reference to iter instead of that to iovec

Signed-off-by: Al Viro

fuse: switch to ->read_iter/->write_iter

2015-04-12T02:29:41+00:00

we just change the calling conventions here; more work to follow.

Signed-off-by: Al Viro

make new_sync_{read,write}() static

2015-04-12T02:29:40+00:00

All places outside of core VFS that checked ->read and ->write for being NULL or
called the methods directly are gone now, so NULL {read,write} with non-NULL
{read,write}_iter will do the right thing in all cases.

Signed-off-by: Al Viro