From: Adrian Hunter <adrian.hunter@nokia.com>
To: Artem Bityutskiy <dedekind1@gmail.com>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"Bityutskiy Artem (Nokia-D/Helsinki)"
<Artem.Bityutskiy@nokia.com>
Subject: Re: [PATCH] UBIFS: kill BKL
Date: Mon, 20 Jul 2009 09:16:31 +0300 [thread overview]
Message-ID: <4A640BBF.10106@nokia.com> (raw)
In-Reply-To: <1248000922-4065-1-git-send-email-dedekind1@gmail.com>
Artem Bityutskiy wrote:
> From: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
>
> The BKL was pushed down from VFS to the file-systems. It used
> to serialize mount/unmount/remount. UBIFS must be safe if several
> file-systems are mounted/unmounted/re-mounted at the same time,
> so kill kick the BKL out of UBIFS.
>
> Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
> ---
Looks like protection is always provided by sb->s_umount
Missing {} below, btw.
> fs/ubifs/super.c | 15 ++-------------
> 1 files changed, 2 insertions(+), 13 deletions(-)
>
> diff --git a/fs/ubifs/super.c b/fs/ubifs/super.c
> index 26d2e0d..4ad992f 100644
> --- a/fs/ubifs/super.c
> +++ b/fs/ubifs/super.c
> @@ -1726,8 +1726,6 @@ static void ubifs_put_super(struct super_block *sb)
> ubifs_msg("un-mount UBI device %d, volume %d", c->vi.ubi_num,
> c->vi.vol_id);
>
> - lock_kernel();
> -
> /*
> * The following asserts are only valid if there has not been a failure
> * of the media. For example, there will be dirty inodes if we failed
> @@ -1792,8 +1790,6 @@ static void ubifs_put_super(struct super_block *sb)
> ubi_close_volume(c->ubi);
> mutex_unlock(&c->umount_mutex);
> kfree(c);
> -
> - unlock_kernel();
> }
>
> static int ubifs_remount_fs(struct super_block *sb, int *flags, char *data)
> @@ -1809,24 +1805,18 @@ static int ubifs_remount_fs(struct super_block *sb, int *flags, char *data)
> return err;
> }
>
> - lock_kernel();
> if ((sb->s_flags & MS_RDONLY) && !(*flags & MS_RDONLY)) {
> if (c->ro_media) {
> ubifs_msg("cannot re-mount due to prior errors");
> - unlock_kernel();
> return -EROFS;
> }
> err = ubifs_remount_rw(c);
> - if (err) {
> - unlock_kernel();
> + if (err)
> return err;
> - }
> } else if (!(sb->s_flags & MS_RDONLY) && (*flags & MS_RDONLY)) {
> - if (c->ro_media) {
> + if (c->ro_media)
Missing {}
> ubifs_msg("cannot re-mount due to prior errors");
> - unlock_kernel();
> return -EROFS;
> - }
> ubifs_remount_ro(c);
> }
>
> @@ -1839,7 +1829,6 @@ static int ubifs_remount_fs(struct super_block *sb, int *flags, char *data)
> }
>
> ubifs_assert(c->lst.taken_empty_lebs > 0);
> - unlock_kernel();
> return 0;
> }
>
next prev parent reply other threads:[~2009-07-20 6:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-19 10:55 [PATCH] UBIFS: kill BKL Artem Bityutskiy
2009-07-20 6:16 ` Adrian Hunter [this message]
2009-07-20 6:27 ` Artem Bityutskiy
2009-07-20 6:29 ` Artem Bityutskiy
2009-07-20 6:35 ` Adrian Hunter
2009-07-20 10:26 ` Artem Bityutskiy
2009-07-20 12:51 ` Christoph Hellwig
2009-07-20 13:22 ` Artem Bityutskiy
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=4A640BBF.10106@nokia.com \
--to=adrian.hunter@nokia.com \
--cc=Artem.Bityutskiy@nokia.com \
--cc=dedekind1@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
/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).