From: Anand Jain <Anand.Jain@oracle.com>
To: Chris Mason <clm@fb.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>,
Sam Thursfield <sam.thursfield@codethink.co.uk>,
johannes.hirte@datenkhaos.de
Subject: Re: [PATCH] Revert "Btrfs: device_list_add() should not update list when
Date: Fri, 19 Sep 2014 18:21:35 +0800 [thread overview]
Message-ID: <541C03AF.1080807@oracle.com> (raw)
In-Reply-To: <541AF37D.5050505@fb.com>
Looks good to me Chris. Thank you.
Reviewed-by: Anand Jain <anand.jain@oracle.com>
On 09/18/2014 11:00 PM, Chris Mason wrote:
>
> Johannes and Sam, could you please confirm this patch fixes your mount
> regression for now? Anand, please make sure I kept the generation check
> properly.
>
> This reverts commit b96de000bc8bc9688b3a2abea4332bd57648a49f.
>
> This commit is triggering failures to mount by subvolume id in some
> configurations. The main problem is how many different ways this
> scanning function is used, both for scanning while mounted and
> unmounted. A proper cleanup is too big for late rcs.
>
> For now, just revert the commit and we'll put a better fix into a later
> merge window.
>
> Signed-off-by: Chris Mason <clm@fb.com>
> ---
> fs/btrfs/volumes.c | 13 ++++++-------
> 1 file changed, 6 insertions(+), 7 deletions(-)
>
> diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c
> index 340a92d..2c2d6d1 100644
> --- a/fs/btrfs/volumes.c
> +++ b/fs/btrfs/volumes.c
> @@ -529,12 +529,12 @@ static noinline int device_list_add(const char *path,
> */
>
> /*
> - * As of now don't allow update to btrfs_fs_device through
> - * the btrfs dev scan cli, after FS has been mounted.
> + * For now, we do allow update to btrfs_fs_device through the
> + * btrfs dev scan cli after FS has been mounted. We're still
> + * tracking a problem where systems fail mount by subvolume id
> + * when we reject replacement on a mounted FS.
> */
> - if (fs_devices->opened) {
> - return -EBUSY;
> - } else {
> + if (!fs_devices->opened && found_transid < device->generation) {
> /*
> * That is if the FS is _not_ mounted and if you
> * are here, that means there is more than one
> @@ -542,8 +542,7 @@ static noinline int device_list_add(const char *path,
> * with larger generation number or the last-in if
> * generation are equal.
> */
> - if (found_transid < device->generation)
> - return -EEXIST;
> + return -EEXIST;
> }
>
> name = rcu_string_strdup(path, GFP_NOFS);
>
next prev parent reply other threads:[~2014-09-19 10:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-18 15:00 [PATCH] Revert "Btrfs: device_list_add() should not update list when Chris Mason
2014-09-19 10:21 ` Anand Jain [this message]
2014-09-19 13:47 ` Sam Thursfield
2014-09-19 13:59 ` 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=541C03AF.1080807@oracle.com \
--to=anand.jain@oracle.com \
--cc=clm@fb.com \
--cc=johannes.hirte@datenkhaos.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=sam.thursfield@codethink.co.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).