From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: [PATCH 10/12] jffs2: call jffs2_write_super from jffs2_sync_fs Date: Mon, 8 Jun 2009 10:08:21 +0200 Message-ID: <20090608080821.GK20735@lst.de> References: <20090608080252.GA20735@lst.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linux-fsdevel@vger.kernel.org To: viro@zeniv.linux.org.uk Return-path: Received: from verein.lst.de ([213.95.11.210]:33443 "EHLO verein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753826AbZFHIIU (ORCPT ); Mon, 8 Jun 2009 04:08:20 -0400 Content-Disposition: inline In-Reply-To: <20090608080252.GA20735@lst.de> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: The call to ->write_super from __sync_filesystem will go away, so make sure jffs2 performs the same actions from inside ->sync_fs. Signed-off-by: Christoph Hellwig Index: vfs-2.6/fs/jffs2/super.c =================================================================== --- vfs-2.6.orig/fs/jffs2/super.c 2009-06-05 16:22:29.959939587 +0200 +++ vfs-2.6/fs/jffs2/super.c 2009-06-05 16:22:49.270946332 +0200 @@ -74,6 +74,8 @@ static int jffs2_sync_fs(struct super_bl { struct jffs2_sb_info *c = JFFS2_SB_INFO(sb); + jffs2_write_super(sb); + mutex_lock(&c->alloc_sem); jffs2_flush_wbuf_pad(c); mutex_unlock(&c->alloc_sem);