From: Marco Stornelli <marco.stornelli@gmail.com>
To: Linux FS Devel <linux-fsdevel@vger.kernel.org>,
Al Viro <viro@ZenIV.linux.org.uk>
Cc: Boaz Harrosh <bharrosh@panasas.com>,
artem.bityutskiy@linux.intel.com, linux-kernel@vger.kernel.org
Subject: [PATCH 1/8] exofs: drop lock/unlock super
Date: Thu, 30 Aug 2012 16:56:11 +0200 [thread overview]
Message-ID: <503F7F0B.4040506@gmail.com> (raw)
Removed lock/unlock super.
Acked-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
Acked-by: Boaz Harrosh <bharrosh@panasas.com>
Signed-off-by: Marco Stornelli <marco.stornelli@gmail.com>
---
fs/exofs/super.c | 4 ----
1 files changed, 0 insertions(+), 4 deletions(-)
diff --git a/fs/exofs/super.c b/fs/exofs/super.c
index dde41a7..c4360b5 100644
--- a/fs/exofs/super.c
+++ b/fs/exofs/super.c
@@ -384,8 +384,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);
@@ -401,8 +399,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);
--
1.7.3.4
next reply other threads:[~2012-08-30 14:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-30 14:56 Marco Stornelli [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-10-06 10:38 [PATCH 1/8] exofs: drop lock/unlock super Marco Stornelli
2012-10-08 21:58 ` Boaz Harrosh
2012-10-08 23:24 ` Al Viro
2012-10-09 15:55 ` Marco Stornelli
2012-10-09 16:40 ` Al Viro
2012-10-09 17:44 ` Theodore Ts'o
2012-10-10 8:04 ` Marco Stornelli
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=503F7F0B.4040506@gmail.com \
--to=marco.stornelli@gmail.com \
--cc=artem.bityutskiy@linux.intel.com \
--cc=bharrosh@panasas.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).