xfs: wait for direct I/O to complete in fsync and write_inode
authorChristoph Hellwig <hch@infradead.org>
Tue, 20 Apr 2010 07:00:59 +0000 (17:00 +1000)
committerAlex Elder <aelder@sgi.com>
Wed, 19 May 2010 14:58:14 +0000 (09:58 -0500)
We need to wait for all pending direct I/O requests before taking care of
metadata in fsync and write_inode.

Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Dave Chinner <david@fromorbit.com>
fs/xfs/linux-2.6/xfs_file.c
fs/xfs/linux-2.6/xfs_super.c

index 42dd3bc..d8fb1b5 100644 (file)
@@ -115,6 +115,8 @@ xfs_file_fsync(
 
        xfs_iflags_clear(ip, XFS_ITRUNCATED);
 
+       xfs_ioend_wait(ip);
+
        /*
         * We always need to make sure that the required inode state is safe on
         * disk.  The inode might be clean but we still might need to force the
index e8ad6dd..e900251 100644 (file)
@@ -1093,6 +1093,7 @@ xfs_fs_write_inode(
                 * the code will only flush the inode if it isn't already
                 * being flushed.
                 */
+               xfs_ioend_wait(ip);
                xfs_ilock(ip, XFS_ILOCK_SHARED);
                if (ip->i_update_core) {
                        error = xfs_log_inode(ip);