All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anand Jain <anand.jain@oracle.com>
To: linux-btrfs@vger.kernel.org
Cc: wqu@suse.com
Subject: [PATCH 1/2] btrfs: add missing BTRFS_SUPER_FLAG define
Date: Mon,  8 Jan 2018 11:05:11 +0800	[thread overview]
Message-ID: <20180108030512.22344-1-anand.jain@oracle.com> (raw)

btrfs-progs uses super flag bit BTRFS_SUPER_FLAG_METADUMP_V2 (1ULL << 34).
So just define that in kernel so that we know its been used. This patch
does not add it to BTRFS_SUPER_FLAG_SUPP yet, and will continue to warn
about unsupported flag.

Signed-off-by: Anand Jain <anand.jain@oracle.com>
---
 include/uapi/linux/btrfs_tree.h | 1 +
 1 file changed, 1 insertion(+)

diff --git a/include/uapi/linux/btrfs_tree.h b/include/uapi/linux/btrfs_tree.h
index 6d6e5da51527..38ab0e06259a 100644
--- a/include/uapi/linux/btrfs_tree.h
+++ b/include/uapi/linux/btrfs_tree.h
@@ -456,6 +456,7 @@ struct btrfs_free_space_header {
 
 #define BTRFS_SUPER_FLAG_SEEDING	(1ULL << 32)
 #define BTRFS_SUPER_FLAG_METADUMP	(1ULL << 33)
+#define BTRFS_SUPER_FLAG_METADUMP_V2	(1ULL << 34)
 
 
 /*
-- 
2.15.0


             reply	other threads:[~2018-01-08  3:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-08  3:05 Anand Jain [this message]
2018-01-08  3:05 ` [PATCH 2/2] btrfs: add support for SUPER_FLAG_CHANGING_FSID in btrfs.ko Anand Jain
2018-01-08  4:55   ` Qu Wenruo
2018-01-08  5:05     ` Anand Jain
2018-01-08  5:10     ` Anand Jain
2018-01-08  5:04   ` [PATCH v2 1/2] " Anand Jain
2018-01-08  5:08     ` Qu Wenruo
2018-01-08  5:13       ` Anand Jain
2018-01-08  5:25         ` Qu Wenruo
2018-01-08  5:58           ` Anand Jain
2018-01-08  7:50             ` Qu Wenruo
2018-01-17 12:45   ` [lkp-robot] [btrfs] d1f6ad52c3: BTRFS error (device md0): SUPER_FLAG_CHANGING_FSID is set kernel test robot
2018-01-18  3:34     ` Anand Jain
2018-01-18  3:34       ` Anand Jain
2018-01-08  4:52 ` [PATCH 1/2] btrfs: add missing BTRFS_SUPER_FLAG define Qu Wenruo

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=20180108030512.22344-1-anand.jain@oracle.com \
    --to=anand.jain@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=wqu@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.