aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorArtem Bityutskiy <artem.bityutskiy@linux.intel.com>2012-05-07 11:45:39 -0400
committerDavid Woodhouse <David.Woodhouse@intel.com>2012-05-14 00:23:01 -0400
commitc3c4a36979c8b68cc35643497e83c7383cd07955 (patch)
tree0fa3511ebc863a9f95a88c60bd3c0cde097cc2fc
parentf4d0b3557582808d5ce9f868e9dfd98f0e769e82 (diff)
jffs2: remove unnecessary GC pass on umount
We do not need to call 'jffs2_write_super()' on unmount. This function causes a GC pass to make sure the current contents is pushed out with the data which we already have on the media. But this is not needed on unmount and only slows unmount down unnecessarily. It is enough to just sync the write-buffer. This call was added by one of the generic VFS rework patch-sets, see 8c85e125124a473d6f3e9bb187b0b84207f81d91. Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com> Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
-rw-r--r--fs/jffs2/super.c3
1 files changed, 0 insertions, 3 deletions
diff --git a/fs/jffs2/super.c b/fs/jffs2/super.c
index 3f1c90c2bdf8..1613cd283042 100644
--- a/fs/jffs2/super.c
+++ b/fs/jffs2/super.c
@@ -333,9 +333,6 @@ static void jffs2_put_super (struct super_block *sb)
333 333
334 jffs2_dbg(2, "%s()\n", __func__); 334 jffs2_dbg(2, "%s()\n", __func__);
335 335
336 if (sb->s_dirt)
337 jffs2_write_super(sb);
338
339 mutex_lock(&c->alloc_sem); 336 mutex_lock(&c->alloc_sem);
340 jffs2_flush_wbuf_pad(c); 337 jffs2_flush_wbuf_pad(c);
341 mutex_unlock(&c->alloc_sem); 338 mutex_unlock(&c->alloc_sem);