From: Anand Jain <anand.jain@oracle.com>
To: linux-btrfs@vger.kernel.org
Cc: dsterba@suse.cz, calestyo@scientia.net, ahferroin7@gmail.com,
1i5t5.duncan@cox.net
Subject: [PATCH 5/7] btrfs-progs: introduce framework version to features
Date: Wed, 25 Nov 2015 20:08:18 +0800 [thread overview]
Message-ID: <1448453300-8449-6-git-send-email-anand.jain@oracle.com> (raw)
In-Reply-To: <1448453300-8449-1-git-send-email-anand.jain@oracle.com>
As discussed in the mailing list this provides a framework to introduce
the feature where mkfs and btrfs-convert can set the default features
as per the given mainline kernel version.
Suggested-by: David Sterba <dsterba@suse.cz>
Signed-off-by: Anand Jain <anand.jain@oracle.com>
---
utils.c | 23 +++++++++++++++++++++++
utils.h | 1 +
2 files changed, 24 insertions(+)
diff --git a/utils.c b/utils.c
index 216efa6..a9b46b8 100644
--- a/utils.c
+++ b/utils.c
@@ -3222,3 +3222,26 @@ int btrfs_features_allowed_by_sysfs(u64 *features)
closedir(dir);
return 0;
}
+
+int btrfs_features_allowed_by_version(char *version, u64 *features)
+{
+ int i;
+ int code;
+ char *ver = strdup(version);
+
+ *features = 0;
+ code = version_to_code(ver);
+ free(ver);
+ if (code < 0)
+ return code;
+
+ for (i = 0; i < ARRAY_SIZE(mkfs_features) - 1; i++) {
+ ver = strdup(mkfs_features[i].min_ker_ver);
+
+ if (code >= version_to_code(ver))
+ *features |= mkfs_features[i].flag;
+
+ free(ver);
+ }
+ return 0;
+}
diff --git a/utils.h b/utils.h
index cb20d73..1418e84 100644
--- a/utils.h
+++ b/utils.h
@@ -106,6 +106,7 @@ void btrfs_process_fs_features(u64 flags);
void btrfs_parse_features_to_string(char *buf, u64 flags);
u64 btrfs_features_allowed_by_kernel(void);
int btrfs_features_allowed_by_sysfs(u64 *features);
+int btrfs_features_allowed_by_version(char *version, u64 *features);
struct btrfs_mkfs_config {
char *label;
--
2.6.2
next prev parent reply other threads:[~2015-11-25 12:08 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-25 12:08 [PATCH 0/7] Let user specify the kernel version for features Anand Jain
2015-11-25 12:08 ` [PATCH 1/7] btrfs-progs: show the version for -O list-all Anand Jain
2015-11-25 12:08 ` [PATCH 2/7] btrfs-progs: add kernel alias for each of the features in the list Anand Jain
2015-11-25 13:36 ` [PATCH V1.1 " Anand Jain
2015-11-25 18:11 ` [PATCH " Liu Bo
2015-11-25 22:52 ` Anand Jain
2015-11-25 12:08 ` [PATCH 3/7] btrfs-progs: make is_numerical non static Anand Jain
2015-11-25 12:08 ` [PATCH 4/7] btrfs-progs: check for numerical in version_to_code() Anand Jain
2015-11-25 12:08 ` Anand Jain [this message]
2015-11-25 12:08 ` [PATCH 6/7] btrfs-progs: add -O comp= option for mkfs.btrfs Anand Jain
2015-11-25 12:08 ` [PATCH 7/7] btrfs-progs: add -O comp= option for btrfs-convert Anand Jain
2015-11-26 2:02 ` [PATCH 0/7] Let user specify the kernel version for features Qu Wenruo
2015-11-26 6:07 ` Anand Jain
2015-11-26 6:53 ` Qu Wenruo
2015-11-26 11:18 ` Anand Jain
2015-11-26 12:31 ` Qu Wenruo
2015-11-26 22:17 ` Anand Jain
2015-11-27 0:44 ` Qu Wenruo
2015-11-27 8:41 ` Anand Jain
2015-11-29 1:21 ` Qu Wenruo
2015-11-30 4:54 ` Anand Jain
2015-11-30 5:46 ` Qu Wenruo
2016-02-03 10:50 ` David Sterba
2016-02-04 1:12 ` Qu Wenruo
2016-02-04 1:42 ` Chris Mason
2015-11-30 5:44 ` potential btrfs-progs clean up Anand Jain
2015-11-30 6:12 ` 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=1448453300-8449-6-git-send-email-anand.jain@oracle.com \
--to=anand.jain@oracle.com \
--cc=1i5t5.duncan@cox.net \
--cc=ahferroin7@gmail.com \
--cc=calestyo@scientia.net \
--cc=dsterba@suse.cz \
--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).