From: Eric Sandeen <sandeen@redhat.com>
Date: Mon, 14 Dec 2009 18:59:59 +0000 (-0600)
Subject: ext3: ext3_mark_recovery_complete() doesn't need to use lock_super
X-Git-Tag: v2.6.33-rc2~18^2~7
X-Git-Url: http://git.openpandora.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=4854a5f0cbb1967fc7db3ea861d97afeea78b88b;p=pandora-kernel.git

ext3: ext3_mark_recovery_complete() doesn't need to use lock_super

The function ext3_mark_recovery_complete() is called from two call
paths: either (a) while mounting the filesystem, in which case there's
no danger of any other CPU calling write_super() until the mount is
completed, and (b) while remounting the filesystem read-write, in
which case the fs core has already locked the superblock.  This also
allows us to take out a very vile unlock_super()/lock_super() pair in
ext3_remount().

Port of ext4 commit a63c9eb2ce6f5028da90f282798232c4f398ceb8 by
Theodore Ts'o <tytso@mit.edu>.

CC: Theodore Ts'o <tytso@mit.edu>
Signed-off-by: Eric Sandeen <sandeen@redhat.com>
Signed-off-by: Jan Kara <jack@suse.cz>
---

Reading git-diff-tree failed