From: Theodore Tso <tytso@mit.edu>
Date: Wed, 12 Nov 2008 21:27:01 +0000 (-0800)
Subject: ext3: Clean up outdated and incorrect comment for ext3_write_super()
X-Git-Tag: v2.6.28-rc5~37
X-Git-Url: http://pilppa.com/gitweb/?a=commitdiff_plain;h=6cdfcc275e40b89fb020da1088ead86a61d33115;p=linux-2.6-omap-h63xx.git

ext3: Clean up outdated and incorrect comment for ext3_write_super()

Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
Cc: <linux-ext4@vger.kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
---

diff --git a/fs/ext3/super.c b/fs/ext3/super.c
index 5dec6d1356c..f6c94f232ec 100644
--- a/fs/ext3/super.c
+++ b/fs/ext3/super.c
@@ -2375,12 +2375,9 @@ int ext3_force_commit(struct super_block *sb)
 /*
  * Ext3 always journals updates to the superblock itself, so we don't
  * have to propagate any other updates to the superblock on disk at this
- * point.  Just start an async writeback to get the buffers on their way
- * to the disk.
- *
- * This implicitly triggers the writebehind on sync().
+ * point.  (We can probably nuke this function altogether, and remove
+ * any mention to sb->s_dirt in all of fs/ext3; eventual cleanup...)
  */
-
 static void ext3_write_super (struct super_block * sb)
 {
 	if (mutex_trylock(&sb->s_lock) != 0)