vfs: Remove syncing from generic_file_direct_write() and generic_file_buffered_write()
authorJan Kara <jack@suse.cz>
Tue, 18 Aug 2009 14:18:20 +0000 (16:18 +0200)
committerJan Kara <jack@suse.cz>
Mon, 14 Sep 2009 15:08:15 +0000 (17:08 +0200)
commitc7b50db21fe8c295092518e224d60b95e69da3b0
treeed73757b475462c4cfccdcf61d95929f4cb32637
parente4dd9de3c66bc7e26c5c7f149a060c5a67cf06a0
vfs: Remove syncing from generic_file_direct_write() and generic_file_buffered_write()

generic_file_direct_write() and generic_file_buffered_write() called
generic_osync_inode() if it was called on O_SYNC file or IS_SYNC inode. But
this is superfluous since generic_file_aio_write() does the syncing as well.
Also XFS and OCFS2 which call these functions directly handle syncing
themselves. So let's have a single place where syncing happens:
generic_file_aio_write().

We slightly change the behavior by syncing only the range of file to which the
write happened for buffered writes but that should be all that is required.

CC: ocfs2-devel@oss.oracle.com
CC: Joel Becker <joel.becker@oracle.com>
CC: Felix Blyakher <felixb@sgi.com>
CC: xfs@oss.sgi.com
Signed-off-by: Jan Kara <jack@suse.cz>
mm/filemap.c