kernel.git/fs/ntfs, branch linux-4.1.y

fs: Give dentry to inode_change_ok() instead of inode

2016-12-23T13:56:35Z

[ Upstream commit 31051c85b5e2aaaf6315f74c72a732673632a905 ] inode_change_ok() will be resposible for clearing capabilities and IMA extended attributes and as such will need dentry. Give it as an argument to inode_change_ok() instead of an inode. Also rename inode_change_ok() to setattr_prepare() to better relect that it does also some modifications in addition to checks. References: CVE-2015-1350 Reviewed-by: Christoph Hellwig Signed-off-by: Jan Kara Signed-off-by: Philipp Hahn Signed-off-by: Sasha Levin

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

2015-04-15T19:06:57Z

that's the bulk of filesystem drivers dealing with inodes of their own Signed-off-by: David Howells Signed-off-by: Al Viro

switch generic_write_checks() to iocb and iter

2015-04-12T02:30:21Z

... 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

generic_write_checks(): drop isblk argument

2015-04-12T02:29:48Z

all remaining callers are passing 0; some just obscure that fact. Signed-off-by: Al Viro

ntfs: move iov_iter_truncate() closer to generic_write_checks()

2015-04-12T02:29:46Z

Signed-off-by: Al Viro

make new_sync_{read,write}() static

2015-04-12T02:29:40Z

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

Merge branch 'iocb' into for-next

2015-04-12T02:24:41Z

NTFS: Version 2.1.32 - Update file write from aio_write to write_iter.

2015-04-12T02:24:33Z

Signed-off-by: Anton Altaparmakov Signed-off-by: Al Viro

fs: move struct kiocb to fs.h

2015-03-26T00:28:11Z

struct kiocb now is a generic I/O container, so move it to fs.h. Also do a #include diet for aio.h while we're at it. Signed-off-by: Christoph Hellwig Signed-off-by: Al Viro

fs: export inode_to_bdi and use it in favor of mapping->backing_dev_info

2015-01-20T21:03:04Z

Now that we got rid of the bdi abuse on character devices we can always use sb->s_bdi to get at the backing_dev_info for a file, except for the block device special case. Export inode_to_bdi and replace uses of mapping->backing_dev_info with it to prepare for the removal of mapping->backing_dev_info. Signed-off-by: Christoph Hellwig Reviewed-by: Tejun Heo Reviewed-by: Jan Kara Signed-off-by: Jens Axboe