From: Anand Jain <anand.jain@oracle.com>
To: David Sterba <dsterba@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: prepare for extensions in compression options
Date: Thu, 27 Jul 2017 15:25:37 +0800 [thread overview]
Message-ID: <ad1a3fdc-fe64-cf84-ba02-746c3eaa0a3b@oracle.com> (raw)
In-Reply-To: <20170717162222.16926-1-dsterba@suse.com>
On 07/18/2017 12:22 AM, David Sterba wrote:
> This is a minimal patch intended to be backported to older kernels.
> We're going to extend the string specifying the compression method and
> this would fail on kernels before that change (the string is compared
> exactly).
>
> Relax the string matching only to the prefix, ie. ignoring anything that
> goes after "zlib" or "lzo", regardless of th format extension we decide
> to use. This applies to the mount options and properties.
>
> That way, patched old kernels could be booted on systems already
> utilizing the new compression spec.
In the view of older kernel with this patch, we need extra logic to
continue to fail bad string after lzo..
----
mount -o compress=lzoJUNK /dev/sdb /btrfs
mount: wrong fs type, bad option, bad superblock on /dev/sdb,
[ 2128.045252] BTRFS error (device sdb): open_ctree failed
----
With this patch. I guess the above mount (or for that matter property
as well) will be successful. ?
Thanks, Anand
> Applicable since commit 63541927c8d11, v3.14.
>
> Signed-off-by: David Sterba <dsterba@suse.com>
> ---
> fs/btrfs/props.c | 4 ++--
> fs/btrfs/super.c | 4 ++--
> 2 files changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/fs/btrfs/props.c b/fs/btrfs/props.c
> index 4b23ae5d0e5c..f41654f05719 100644
> --- a/fs/btrfs/props.c
> +++ b/fs/btrfs/props.c
> @@ -408,9 +408,9 @@ static int prop_compression_apply(struct inode *inode,
> return 0;
> }
>
> - if (!strncmp("lzo", value, len))
> + if (!strncmp("lzo", value, 3))
> type = BTRFS_COMPRESS_LZO;
> - else if (!strncmp("zlib", value, len))
> + else if (!strncmp("zlib", value, 4))
> type = BTRFS_COMPRESS_ZLIB;
> else
> return -EINVAL;
> diff --git a/fs/btrfs/super.c b/fs/btrfs/super.c
> index 74e47794e63f..147330454c17 100644
> --- a/fs/btrfs/super.c
> +++ b/fs/btrfs/super.c
> @@ -498,14 +498,14 @@ int btrfs_parse_options(struct btrfs_fs_info *info, char *options,
> btrfs_test_opt(info, FORCE_COMPRESS);
> if (token == Opt_compress ||
> token == Opt_compress_force ||
> - strcmp(args[0].from, "zlib") == 0) {
> + strncmp(args[0].from, "zlib", 4) == 0) {
> compress_type = "zlib";
> info->compress_type = BTRFS_COMPRESS_ZLIB;
> btrfs_set_opt(info->mount_opt, COMPRESS);
> btrfs_clear_opt(info->mount_opt, NODATACOW);
> btrfs_clear_opt(info->mount_opt, NODATASUM);
> no_compress = 0;
> - } else if (strcmp(args[0].from, "lzo") == 0) {
> + } else if (strncmp(args[0].from, "lzo", 3) == 0) {
> compress_type = "lzo";
> info->compress_type = BTRFS_COMPRESS_LZO;
> btrfs_set_opt(info->mount_opt, COMPRESS);
>
next prev parent reply other threads:[~2017-07-27 7:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-17 16:22 [PATCH] btrfs: prepare for extensions in compression options David Sterba
2017-07-27 7:25 ` Anand Jain [this message]
2017-07-27 15:26 ` David Sterba
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=ad1a3fdc-fe64-cf84-ba02-746c3eaa0a3b@oracle.com \
--to=anand.jain@oracle.com \
--cc=dsterba@suse.com \
--cc=linux-btrfs@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).