exofs: drop lock/unlock super

Removed lock/unlock super.

Acked-by Artem Bityutskiy <[email protected]>

Acked-by Boaz Harrosh <[email protected]>

Signed-off-by Marco Stornelli <[email protected]>

---
 fs/exofs/super.c |    4 ----
 1 files changed, 0 insertions(+), 4 deletions(-)

fs/exofs/super.c +0 -4

index 59e3bbf..5e59280 100644
@@ -389,8 +389,6 @@ static int exofs_sync_fs(struct super_block *sb, int wait)
 	if (unlikely(ret))
 		goto out;
 
-	lock_super(sb);
-
 	ios->length = offsetof(struct exofs_fscb, s_dev_table_oid);
 	memset(fscb, 0, ios->length);
 	fscb->s_nextid = cpu_to_le64(sbi->s_nextid);

@@ -406,8 +404,6 @@ static int exofs_sync_fs(struct super_block *sb, int wait)
 	if (unlikely(ret))
 		EXOFS_ERR("%s: ore_write failed.\n", __func__);
 
-
-	unlock_super(sb);
 out:
 	EXOFS_DBGMSG("s_nextid=0x%llx ret=%d\n", _LLU(sbi->s_nextid), ret);
 	ore_put_io_state(ios);

Hi Marco

I was sure you guys where pushing this patch through some vfs tree. (Hence my Acked-by below). I have just sent Linus a pull request for the 3.7 Kernel. I could perhaps append this one and resend.

I do want this patch, and it is completely independent and can go through my tree. Please tell me what do you want to do with this patch, should I push it? Or are you pushing it through Al

Quoted 7 lines

Hi Marco

I was sure you guys where pushing this patch through some vfs tree. (Hence my Acked-by below). I have just sent Linus a pull request for the 3.7 Kernel. I could perhaps append this one and resend.

Quoted 3 lines

I do want this patch, and it is completely independent and can go through my tree. Please tell me what do you want to do with this patch, should I push it? Or are you pushing it through Al

This series is slated for tonight push; I'm testing the tree right now...

Thanks Al. For me there aren't problems to push it via Al or via other trees. For example the patch for ext4 is in Ted's tree. You tell me what you want and I do it :)

Quoted 4 lines

Thanks Al. For me there aren't problems to push it via Al or via other trees. For example the patch for ext4 is in Ted's tree. You tell me what you want and I do it :)

Um... Then I'd better drop the ext4 part and hold the final one back, right? Are there other commits I need to skip to avoid duplicates with the stuff already in other trees?