From: cwillu <cwillu@cwillu.com>
To: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
Linux Kernel Maling List <linux-kernel@vger.kernel.org>,
Linux FS Maling List <linux-fsdevel@vger.kernel.org>,
Chris Mason <chris.mason@fusionio.com>,
linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 07/16] btrfs: nuke write_super from comments
Date: Wed, 25 Jul 2012 09:46:49 -0600 [thread overview]
Message-ID: <CAE5mzvg178UUj4eRmL-VE+=jXSnBJvAUgNPooY3f2ihbwSbBOg@mail.gmail.com> (raw)
In-Reply-To: <1343229134-29487-8-git-send-email-artem.bityutskiy@linux.intel.com>
> diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c
> index ecaad40..9f2416c 100644
> --- a/fs/btrfs/volumes.c
> +++ b/fs/btrfs/volumes.c
> @@ -1738,10 +1738,6 @@ int btrfs_init_new_device(struct btrfs_root *root, char *device_path)
>
> device->fs_devices = root->fs_info->fs_devices;
>
> - /*
> - * we don't want write_supers to jump in here with our device
> - * half setup
> - */
> mutex_lock(&root->fs_info->fs_devices->device_list_mutex);
> list_add_rcu(&device->dev_list, &root->fs_info->fs_devices->devices);
> list_add(&device->dev_alloc_list,
Is the locking still required for approximately the same reason?
next prev parent reply other threads:[~2012-07-25 15:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1343229134-29487-1-git-send-email-artem.bityutskiy@linux.intel.com>
2012-07-25 15:12 ` [PATCH 07/16] btrfs: nuke write_super from comments Artem Bityutskiy
2012-07-25 15:46 ` cwillu [this message]
2012-07-25 16:06 ` Artem Bityutskiy
2012-07-25 15:12 ` [PATCH 08/16] btrfs: nuke pdflush " 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='CAE5mzvg178UUj4eRmL-VE+=jXSnBJvAUgNPooY3f2ihbwSbBOg@mail.gmail.com' \
--to=cwillu@cwillu.com \
--cc=artem.bityutskiy@linux.intel.com \
--cc=chris.mason@fusionio.com \
--cc=linux-btrfs@vger.kernel.org \
--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).