linux-toradex.git/fs/fat/file.c, branch v3.4.16

fat: propagate umode_t

2012-01-04T03:55:09+00:00

Signed-off-by: Al Viro

vfs: mnt_drop_write_file()

2012-01-04T03:52:40+00:00

new helper (wrapper around mnt_drop_write()) to be used in pair with
mnt_want_write_file().

Signed-off-by: Al Viro

switch a bunch of places to mnt_want_write_file()

2012-01-04T03:52:35+00:00

it's both faster (in case when file has been opened for write) and cleaner.

Signed-off-by: Al Viro

fs: push i_mutex and filemap_write_and_wait down into ->fsync() handlers

2011-07-21T00:47:59+00:00

Btrfs needs to be able to control how filemap_write_and_wait_range() is called
in fsync to make it less of a painful operation, so push down taking i_mutex and
the calling of filemap_write_and_wait() down into the ->fsync() handlers.  Some
file systems can drop taking the i_mutex altogether it seems, like ext3 and
ocfs2.  For correctness sake I just pushed everything down in all cases to make
sure that we keep the current behavior the same for everybody, and then each
individual fs maintainer can make up their mind about what to do from there.
Thanks,

Acked-by: Jan Kara 
Signed-off-by: Josef Bacik 
Signed-off-by: Al Viro

fs: move inode_dio_wait calls into ->setattr

2011-07-21T00:47:47+00:00

Let filesystems handle waiting for direct I/O requests themselves instead
of doing it beforehand.  This means filesystem-specific locks to prevent
new dio referenes from appearing can be held.  This is important to allow
generalizing i_dio_count to non-DIO_LOCKING filesystems.

Signed-off-by: Christoph Hellwig 
Signed-off-by: Al Viro

fat: remove i_alloc_sem abuse

2011-07-21T00:47:44+00:00

Add a new rw_semaphore to protect bmap against truncate.  Previous
i_alloc_sem was abused for this, but it's going away in this series.

Note that we can't simply use i_mutex, given that the swapon code
calls ->bmap under it.

Signed-off-by: Christoph Hellwig 
Signed-off-by: Al Viro

fat: Fix corrupt inode flags when remove ATTR_SYS flag

2011-05-31T10:42:24+00:00

We are clearly missing '~' in fat_ioctl_set_attributes().

Cc: 
Reported-by: Dmitry Dmitriev 
Signed-off-by: OGAWA Hirofumi

check ATTR_SIZE contraints in inode_change_ok

2010-08-09T20:47:39+00:00

Make sure we check the truncate constraints early on in ->setattr by adding
those checks to inode_change_ok.  Also clean up and document inode_change_ok
to make this obvious.

As a fallout we don't have to call inode_newsize_ok from simple_setsize and
simplify it down to a truncate_setsize which doesn't return an error.  This
simplifies a lot of setattr implementations and means we use truncate_setsize
almost everywhere.  Get rid of fat_setsize now that it's trivial and mark
ext2_setsize static to make the calling convention obvious.

Keep the inode_newsize_ok in vmtruncate for now as all callers need an
audit for its removal anyway.

Note: setattr code in ecryptfs doesn't call inode_change_ok at all and
needs a deeper audit, but that is left for later.

Signed-off-by: Christoph Hellwig 
Signed-off-by: Al Viro

always call inode_change_ok early in ->setattr

2010-08-09T20:47:38+00:00

Make sure we call inode_change_ok before doing any changes in ->setattr,
and make sure to call it even if our fs wants to ignore normal UNIX
permissions, but use the ATTR_FORCE to skip those.

Signed-off-by: Christoph Hellwig 
Signed-off-by: Al Viro

rename generic_setattr

2010-08-09T20:47:35+00:00

Despite its name it's now a generic implementation of ->setattr, but
rather a helper to copy attributes from a struct iattr to the inode.
Rename it to setattr_copy to reflect this fact.

Signed-off-by: Christoph Hellwig 
Signed-off-by: Al Viro