From: Jan Blunck <jblunck@suse.de>
To: linux-fsdevel@vger.kernel.org
Cc: Matthew Wilcox <matthew@wil.cx>,
linux-kernel@vger.kernel.org, Jan Blunck <jblunck@suse.de>,
Chris Mason <chris.mason@oracle.com>,
Christoph Hellwig <hch@lst.de>, Yan Zheng <zheng.yan@oracle.com>,
Al Viro <viro@zeniv.linux.org.uk>, Sage Weil <sage@newdream.net>,
linux-btrfs@vger.kernel.org
Subject: [PATCH 12/27] BKL: Remove BKL from btrfs
Date: Mon, 2 Nov 2009 11:04:52 +0100 [thread overview]
Message-ID: <1257156307-24175-13-git-send-email-jblunck@suse.de> (raw)
In-Reply-To: <1257156307-24175-1-git-send-email-jblunck@suse.de>
BKL is only used in get_sb. It is safe to remove it.
Signed-off-by: Jan Blunck <jblunck@suse.de>
---
fs/btrfs/super.c | 8 +-------
1 files changed, 1 insertions(+), 7 deletions(-)
diff --git a/fs/btrfs/super.c b/fs/btrfs/super.c
index e5cd2cf..752a546 100644
--- a/fs/btrfs/super.c
+++ b/fs/btrfs/super.c
@@ -480,17 +480,13 @@ static int btrfs_get_sb(struct file_system_type *fs_type, int flags,
fmode_t mode = FMODE_READ;
int error = 0;
- lock_kernel();
-
if (!(flags & MS_RDONLY))
mode |= FMODE_WRITE;
error = btrfs_parse_early_options(data, mode, fs_type,
&subvol_name, &fs_devices);
- if (error) {
- unlock_kernel();
+ if (error)
return error;
- }
error = btrfs_scan_one_device(dev_name, mode, fs_type, &fs_devices);
if (error)
@@ -559,7 +555,6 @@ static int btrfs_get_sb(struct file_system_type *fs_type, int flags,
mnt->mnt_root = root;
kfree(subvol_name);
- unlock_kernel();
return 0;
error_s:
@@ -568,7 +563,6 @@ error_close_devices:
btrfs_close_devices(fs_devices);
error_free_subvol_name:
kfree(subvol_name);
- unlock_kernel();
return error;
}
--
1.6.4.2
next parent reply other threads:[~2009-11-02 10:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1257156307-24175-1-git-send-email-jblunck@suse.de>
2009-11-02 10:04 ` Jan Blunck [this message]
2009-11-02 12:13 ` [PATCH 12/27] BKL: Remove BKL from btrfs Chris Mason
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=1257156307-24175-13-git-send-email-jblunck@suse.de \
--to=jblunck@suse.de \
--cc=chris.mason@oracle.com \
--cc=hch@lst.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=sage@newdream.net \
--cc=viro@zeniv.linux.org.uk \
--cc=zheng.yan@oracle.com \
/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