linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: Eric Sandeen <sandeen@redhat.com>,
	linux-btrfs <linux-btrfs@vger.kernel.org>
Cc: Roman Mamedov <rm@romanrm.net>
Subject: Re: [PATCH] btrfs: fix nossd and ssd_spread mount option regression
Date: Mon, 30 Jun 2014 09:57:38 +0800	[thread overview]
Message-ID: <53B0C412.1030207@cn.fujitsu.com> (raw)
In-Reply-To: <53ADE727.5000400@redhat.com>


Oh, my bad, sorry for the SSD related mount options mess.

Thanks for the patch fixing the bug, comments inlined below.
-------- Original Message --------
Subject: [PATCH] btrfs: fix nossd and ssd_spread mount option regression
From: Eric Sandeen <sandeen@redhat.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Date: 2014年06月28日 05:50
> The commit
>
> 0780253 btrfs: Cleanup the btrfs_parse_options for remount.
>
> broke ssd options quite badly; it stopped making ssd_spread
> imply ssd, and it made "nossd" unsettable.
>
> Put things back at least as well as they were before
> (though ssd mount option handling is still pretty odd:
> # mount -o "nossd,ssd_spread" works?)
>
> Reported-by: Roman Mamedov <rm@romanrm.net>
> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
> ---
>
> I've tested this insofar as I was actually able to mount with
> nossd,and see it reflected in /proc/mounts.
>
> If SSD_SPREAD is set, show_options() won't show you the ssd
> option, so that's not totally obvious.  Still, this is what
> the code did before the regression.
>
> diff --git a/fs/btrfs/super.c b/fs/btrfs/super.c
> index 4662d92..0e8edcc 100644
> --- a/fs/btrfs/super.c
> +++ b/fs/btrfs/super.c
> @@ -522,9 +522,10 @@ int btrfs_parse_options(struct btrfs_root *root, char *options)
>   		case Opt_ssd_spread:
>   			btrfs_set_and_info(root, SSD_SPREAD,
>   					   "use spread ssd allocation scheme");
> +			btrfs_set_opt(info->mount_opt, SSD);
>   			break;
>   		case Opt_nossd:
> -			btrfs_clear_and_info(root, NOSSD,
> +			btrfs_set_and_info(root, NOSSD,
>   					     "not using ssd allocation scheme");
>   			btrfs_clear_opt(info->mount_opt, SSD);
Since ssd_spread implies ssd, so nossd should also clear ssd_spread.
So btrfs_clear_opt(info->mount_opt, SSD_SPREAD) is also needed.

Thanks,
Qu
>   			break;
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html



      reply	other threads:[~2014-06-30  1:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-27 21:50 [PATCH] btrfs: fix nossd and ssd_spread mount option regression Eric Sandeen
2014-06-30  1:57 ` Qu Wenruo [this message]

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=53B0C412.1030207@cn.fujitsu.com \
    --to=quwenruo@cn.fujitsu.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=rm@romanrm.net \
    --cc=sandeen@redhat.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;
as well as URLs for NNTP newsgroup(s).