linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tao Ma <tao.ma@oracle.com>
To: Josef Bacik <josef@redhat.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Btrfs-progs: fix incompat flags
Date: Fri, 02 Apr 2010 14:10:53 +0800	[thread overview]
Message-ID: <4BB58A6D.7030505@oracle.com> (raw)
In-Reply-To: <20100401191744.GC21486@dhcp231-156.rdu.redhat.com>

Hi Josef,

Josef Bacik wrote:
> I forgot to add BTRFS_FEATURE_INCOMPAT_DEFAULT_SUBVOL to the incompat flags in
> btrfs-progs.  This adds it so that our tools don't freak out when touching a fs
> with the default subvolume changed.  Thanks,
> 
> Signed-off-by: Josef Bacik <josef@redhat.com>
> ---
>  ctree.h |    4 +++-
>  1 files changed, 3 insertions(+), 1 deletions(-)
> 
> diff --git a/ctree.h b/ctree.h
> index 64ecf12..b79e238 100644
> --- a/ctree.h
> +++ b/ctree.h
> @@ -350,11 +350,13 @@ struct btrfs_super_block {
>   * ones specified below then we will fail to mount
>   */
>  #define BTRFS_FEATURE_INCOMPAT_MIXED_BACKREF	(1ULL << 0)
> +#define BTRFS_FEATURE_INCOMPAT_DEFAULT_SUBVOL	(2ULL << 0)
I am not familiar with btrfs, but I guess the natural way is
+#define BTRFS_FEATURE_INCOMPAT_DEFAULT_SUBVOL	(1ULL << 1) ?
>  
>  #define BTRFS_FEATURE_COMPAT_SUPP		0ULL
>  #define BTRFS_FEATURE_COMPAT_RO_SUPP		0ULL
>  #define BTRFS_FEATURE_INCOMPAT_SUPP		\
> -	BTRFS_FEATURE_INCOMPAT_MIXED_BACKREF
> +	(BTRFS_FEATURE_INCOMPAT_MIXED_BACKREF |	\
> +	 BTRFS_FEATURE_INCOMPAT_DEFAULT_SUBVOL)
>  
>  /*
>   * A leaf is full of items. offset and size tell us where to find

Regards,
Tao

      reply	other threads:[~2010-04-02  6:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-01 19:17 [PATCH] Btrfs-progs: fix incompat flags Josef Bacik
2010-04-02  6:10 ` Tao Ma [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=4BB58A6D.7030505@oracle.com \
    --to=tao.ma@oracle.com \
    --cc=josef@redhat.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).