From: Theodore Ts'o <tytso@mit.edu>
Date: Fri, 1 May 2009 05:59:42 +0000 (-0400)
Subject: ext4: ext4_mark_recovery_complete() doesn't need to use lock_super
X-Git-Tag: v2.6.31-rc1~396^2~38
X-Git-Url: http://git.openpandora.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=a63c9eb2ce6f5028da90f282798232c4f398ceb8;p=pandora-kernel.git

ext4: ext4_mark_recovery_complete() doesn't need to use lock_super

The function ext4_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
ext4_remount().

Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
---

Reading git-diff-tree failed