linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anand Jain <anand.jain@oracle.com>
To: linux-btrfs@vger.kernel.org
Cc: wqu@suse.com
Subject: [PATCH V4 0/3] Add missing flags in the kernel
Date: Tue, 9 Jan 2018 10:32:36 +0800	[thread overview]
Message-ID: <ad6d353e-ba02-3d1f-cff8-23b5a3fb8016@oracle.com> (raw)
In-Reply-To: <20180109010543.16053-1-anand.jain@oracle.com>

(added reroll count in the $subject)

v3->v4:
Patch reordered.
Add BTRFS_SUPER_FLAG_METADUMP_V2 to BTRFS_SUPER_FLAG_SUPP

v2->v3:
Modify BTRFS_SUPER_FLAG_SUPP so that it would fail instead of warn.

v1->v2:
Fail to mount if BTRFS_SUPER_FLAG_CHANGING_FSID is set.

Following bits are already used in user land, so bring it to the kernel
as well.

#define BTRFS_SUPER_FLAG_METADUMP_V2   (1ULL << 34)
#define BTRFS_SUPER_FLAG_CHANGING_FSID (1ULL << 35)

Anand Jain (3):
   btrfs: define SUPER_FLAG_METADUMP_V2
   btrfs: add support for SUPER_FLAG_CHANGING_FSID in btrfs.ko
   btrfs: fail mount when sb flag is not in BTRFS_SUPER_FLAG_SUPP

  fs/btrfs/disk-io.c              | 9 ++++++---
  include/uapi/linux/btrfs_tree.h | 2 ++
  2 files changed, 8 insertions(+), 3 deletions(-)

-- 
2.15.0

      parent reply	other threads:[~2018-01-09  2:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-09  1:05 [PATCH 0/3] Add missing flags in the kernel Anand Jain
2018-01-09  1:05 ` [PATCH 1/3] btrfs: define SUPER_FLAG_METADUMP_V2 Anand Jain
2018-01-09 16:53   ` David Sterba
2018-01-09  1:05 ` [PATCH 2/3] btrfs: add support for SUPER_FLAG_CHANGING_FSID in btrfs.ko Anand Jain
2018-01-09 16:58   ` David Sterba
2018-01-09  1:05 ` [PATCH 3/3] btrfs: fail mount when sb flag is not in BTRFS_SUPER_FLAG_SUPP Anand Jain
2018-01-09 16:57   ` David Sterba
2018-01-09  2:32 ` Anand Jain [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=ad6d353e-ba02-3d1f-cff8-23b5a3fb8016@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 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).