Josef Bacik 02c24a8218 fs: push i_mutex and filemap_write_and_wait down into ->fsync() handlers ... 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 <jack@suse.cz> Signed-off-by: Josef Bacik <josef@redhat.com> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>		2011-07-20 20:47:59 -04:00
..
cache.c
cnode.c
coda_cache.h
coda_fs_i.h
coda_int.h	fs: push i_mutex and filemap_write_and_wait down into ->fsync() handlers	2011-07-20 20:47:59 -04:00
coda_linux.c
coda_linux.h	->permission() sanitizing: don't pass flags to ->permission()	2011-07-20 01:43:24 -04:00
dir.c	don't open-code parent_ino() in assorted ->readdir()	2011-07-20 20:47:54 -04:00
file.c	fs: push i_mutex and filemap_write_and_wait down into ->fsync() handlers	2011-07-20 20:47:59 -04:00
inode.c
Kconfig
Makefile
pioctl.c	->permission() sanitizing: don't pass flags to ->permission()	2011-07-20 01:43:24 -04:00
psdev.c
symlink.c
sysctl.c	codafs: fix build break when CONFIG_PROC_SYSCTL=n	2011-03-25 17:45:16 -07:00
upcall.c