aboutsummaryrefslogtreecommitdiffstats
path: root/fs
diff options
context:
space:
mode:
authorChristoph Hellwig <hch@lst.de>2009-06-08 10:08:54 +0200
committerAl Viro <viro@zeniv.linux.org.uk>2009-06-11 21:36:17 -0400
commit0c95ee190e1dea60c55c834d14695341085c9b7b (patch)
tree2d0899f7aa04acc0679a760e6710c8605745ac92 /fs
parentd731e06323cb705003e4172ec209e469be4c18e1 (diff)
downloadkernel_samsung_aries-0c95ee190e1dea60c55c834d14695341085c9b7b.zip
kernel_samsung_aries-0c95ee190e1dea60c55c834d14695341085c9b7b.tar.gz
kernel_samsung_aries-0c95ee190e1dea60c55c834d14695341085c9b7b.tar.bz2
remove the call to ->write_super in __sync_filesystem
Now that all filesystems provide ->sync_fs methods we can change __sync_filesystem to only call ->sync_fs. This gives us a clear separation between periodic writeouts which are driven by ->write_super and data integrity syncs that go through ->sync_fs. (modulo file_fsync which is also going away) Signed-off-by: Christoph Hellwig <hch@lst.de> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Diffstat (limited to 'fs')
-rw-r--r--fs/sync.c2
1 files changed, 0 insertions, 2 deletions
diff --git a/fs/sync.c b/fs/sync.c
index e9d56f6..dd20002 100644
--- a/fs/sync.c
+++ b/fs/sync.c
@@ -33,8 +33,6 @@ static int __sync_filesystem(struct super_block *sb, int wait)
else
sync_quota_sb(sb, -1);
sync_inodes_sb(sb, wait);
- if (sb->s_dirt && sb->s_op->write_super)
- sb->s_op->write_super(sb);
if (sb->s_op->sync_fs)
sb->s_op->sync_fs(sb, wait);
return __sync_blockdev(sb->s_bdev, wait);