From: Liu Bo <bo.li.liu@oracle.com>
To: Jeff Mahoney <jeffm@suse.com>
Cc: Btrfs Development List <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH 4/8] btrfs: uapi/linux/btrfs.h migration, move feature flags
Date: Wed, 27 Apr 2016 14:08:09 -0700 [thread overview]
Message-ID: <20160427210809.GG15822@localhost.localdomain> (raw)
In-Reply-To: <1459541670-4097-5-git-send-email-jeffm@suse.com>
On Fri, Apr 01, 2016 at 04:14:26PM -0400, Jeff Mahoney wrote:
> The compat/compat_ro/incompat feature flags are used by the feature set/get
> ioctls.
>
Reviewed-by: Liu Bo <bo.li.liu@oracle.com>
Thanks,
-liubo
> Signed-off-by: Jeff Mahoney <jeffm@suse.com>
> ---
> fs/btrfs/ctree.h | 25 -------------------------
> include/uapi/linux/btrfs.h | 31 +++++++++++++++++++++++++++++++
> 2 files changed, 31 insertions(+), 25 deletions(-)
>
> diff --git a/fs/btrfs/ctree.h b/fs/btrfs/ctree.h
> index c228b39..378482c 100644
> --- a/fs/btrfs/ctree.h
> +++ b/fs/btrfs/ctree.h
> @@ -506,31 +506,6 @@ struct btrfs_super_block {
> * Compat flags that we support. If any incompat flags are set other than the
> * ones specified below then we will fail to mount
> */
> -#define BTRFS_FEATURE_COMPAT_RO_FREE_SPACE_TREE (1ULL << 0)
> -
> -#define BTRFS_FEATURE_INCOMPAT_MIXED_BACKREF (1ULL << 0)
> -#define BTRFS_FEATURE_INCOMPAT_DEFAULT_SUBVOL (1ULL << 1)
> -#define BTRFS_FEATURE_INCOMPAT_MIXED_GROUPS (1ULL << 2)
> -#define BTRFS_FEATURE_INCOMPAT_COMPRESS_LZO (1ULL << 3)
> -/*
> - * some patches floated around with a second compression method
> - * lets save that incompat here for when they do get in
> - * Note we don't actually support it, we're just reserving the
> - * number
> - */
> -#define BTRFS_FEATURE_INCOMPAT_COMPRESS_LZOv2 (1ULL << 4)
> -
> -/*
> - * older kernels tried to do bigger metadata blocks, but the
> - * code was pretty buggy. Lets not let them try anymore.
> - */
> -#define BTRFS_FEATURE_INCOMPAT_BIG_METADATA (1ULL << 5)
> -
> -#define BTRFS_FEATURE_INCOMPAT_EXTENDED_IREF (1ULL << 6)
> -#define BTRFS_FEATURE_INCOMPAT_RAID56 (1ULL << 7)
> -#define BTRFS_FEATURE_INCOMPAT_SKINNY_METADATA (1ULL << 8)
> -#define BTRFS_FEATURE_INCOMPAT_NO_HOLES (1ULL << 9)
> -
> #define BTRFS_FEATURE_COMPAT_SUPP 0ULL
> #define BTRFS_FEATURE_COMPAT_SAFE_SET 0ULL
> #define BTRFS_FEATURE_COMPAT_SAFE_CLEAR 0ULL
> diff --git a/include/uapi/linux/btrfs.h b/include/uapi/linux/btrfs.h
> index 0316e23..de98717 100644
> --- a/include/uapi/linux/btrfs.h
> +++ b/include/uapi/linux/btrfs.h
> @@ -222,6 +222,37 @@ struct btrfs_ioctl_fs_info_args {
> __u64 reserved[122]; /* pad to 1k */
> };
>
> +/*
> + * feature flags
> + *
> + * Used by:
> + * struct btrfs_ioctl_feature_flags
> + */
> +#define BTRFS_FEATURE_COMPAT_RO_FREE_SPACE_TREE (1ULL << 0)
> +
> +#define BTRFS_FEATURE_INCOMPAT_MIXED_BACKREF (1ULL << 0)
> +#define BTRFS_FEATURE_INCOMPAT_DEFAULT_SUBVOL (1ULL << 1)
> +#define BTRFS_FEATURE_INCOMPAT_MIXED_GROUPS (1ULL << 2)
> +#define BTRFS_FEATURE_INCOMPAT_COMPRESS_LZO (1ULL << 3)
> +/*
> + * some patches floated around with a second compression method
> + * lets save that incompat here for when they do get in
> + * Note we don't actually support it, we're just reserving the
> + * number
> + */
> +#define BTRFS_FEATURE_INCOMPAT_COMPRESS_LZOv2 (1ULL << 4)
> +
> +/*
> + * older kernels tried to do bigger metadata blocks, but the
> + * code was pretty buggy. Lets not let them try anymore.
> + */
> +#define BTRFS_FEATURE_INCOMPAT_BIG_METADATA (1ULL << 5)
> +
> +#define BTRFS_FEATURE_INCOMPAT_EXTENDED_IREF (1ULL << 6)
> +#define BTRFS_FEATURE_INCOMPAT_RAID56 (1ULL << 7)
> +#define BTRFS_FEATURE_INCOMPAT_SKINNY_METADATA (1ULL << 8)
> +#define BTRFS_FEATURE_INCOMPAT_NO_HOLES (1ULL << 9)
> +
> struct btrfs_ioctl_feature_flags {
> __u64 compat_flags;
> __u64 compat_ro_flags;
> --
> 2.7.1
>
> --
> 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
next prev parent reply other threads:[~2016-04-27 21:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-01 20:14 [PATCH 0/8] btrfs: uapi migration for user-visible API components Jeff Mahoney
2016-04-01 20:14 ` [PATCH 1/8] btrfs: uapi/linux/btrfs.h migration, move BTRFS_LABEL_SIZE Jeff Mahoney
2016-04-27 19:23 ` Liu Bo
2016-04-01 20:14 ` [PATCH 2/8] btrfs: uapi/linux/btrfs.h migration, qgroup limit flags Jeff Mahoney
2016-04-27 19:24 ` Liu Bo
2016-04-01 20:14 ` [PATCH 3/8] btrfs: uapi/linux/btrfs.h migration, document subvol flags Jeff Mahoney
2016-04-27 20:27 ` Liu Bo
2016-04-01 20:14 ` [PATCH 4/8] btrfs: uapi/linux/btrfs.h migration, move feature flags Jeff Mahoney
2016-04-27 21:08 ` Liu Bo [this message]
2016-04-01 20:14 ` [PATCH 5/8] btrfs: uapi/linux/btrfs.h migration, move balance flags Jeff Mahoney
2016-04-27 21:09 ` Liu Bo
2016-04-01 20:14 ` [PATCH 6/8] btrfs: uapi/linux/btrfs.h migration, move struct btrfs_ioctl_defrag_range_args Jeff Mahoney
2016-04-27 21:10 ` Liu Bo
2016-04-01 20:14 ` [PATCH 7/8] btrfs: uapi/linux/btrfs_tree.h migration, item types and defines Jeff Mahoney
2016-04-27 21:12 ` Liu Bo
2016-04-01 20:14 ` [PATCH 8/8] btrfs: uapi/linux/btrfs_tree.h, use __u8 and __u64 Jeff Mahoney
2016-04-27 21:12 ` Liu Bo
2016-04-27 19:37 ` [PATCH 0/8] btrfs: uapi migration for user-visible API components Josef Bacik
2016-04-27 22:42 ` 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=20160427210809.GG15822@localhost.localdomain \
--to=bo.li.liu@oracle.com \
--cc=jeffm@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).