From: Radek Pazdera <rpazdera@redhat.com>
To: linux-ext4@vger.kernel.org
Cc: lczerner@redhat.com, kasparek@fit.vutbr.cz,
Radek Pazdera <rpazdera@redhat.com>
Subject: [PATCH 1/3] libext2fs: Adding itree feature flag
Date: Sat, 4 May 2013 23:35:08 +0200 [thread overview]
Message-ID: <1367703310-3842-2-git-send-email-rpazdera@redhat.com> (raw)
In-Reply-To: <1367703310-3842-1-git-send-email-rpazdera@redhat.com>
This commit reserves a flag for the itree read-only compatible feature.
EXT4_FEATURE_RO_COMPAT_ITREE 0x1000
Signed-off-by: Radek Pazdera <rpazdera@redhat.com>
---
lib/e2p/feature.c | 2 ++
lib/ext2fs/ext2_fs.h | 1 +
2 files changed, 3 insertions(+)
diff --git a/lib/e2p/feature.c b/lib/e2p/feature.c
index 70815ef..9b15679 100644
--- a/lib/e2p/feature.c
+++ b/lib/e2p/feature.c
@@ -66,6 +66,8 @@ static struct feature feature_list[] = {
"metadata_csum"},
{ E2P_FEATURE_RO_INCOMPAT, EXT4_FEATURE_RO_COMPAT_REPLICA,
"replica" },
+ { E2P_FEATURE_RO_INCOMPAT, EXT4_FEATURE_RO_COMPAT_ITREE,
+ "itree" },
{ E2P_FEATURE_INCOMPAT, EXT2_FEATURE_INCOMPAT_COMPRESSION,
"compression" },
diff --git a/lib/ext2fs/ext2_fs.h b/lib/ext2fs/ext2_fs.h
index 0c0bbcb..be711ce 100644
--- a/lib/ext2fs/ext2_fs.h
+++ b/lib/ext2fs/ext2_fs.h
@@ -739,6 +739,7 @@ struct ext2_super_block {
*/
#define EXT4_FEATURE_RO_COMPAT_METADATA_CSUM 0x0400
#define EXT4_FEATURE_RO_COMPAT_REPLICA 0x0800
+#define EXT4_FEATURE_RO_COMPAT_ITREE 0x1000
#define EXT2_FEATURE_INCOMPAT_COMPRESSION 0x0001
#define EXT2_FEATURE_INCOMPAT_FILETYPE 0x0002
--
1.7.11.7
next prev parent reply other threads:[~2013-05-04 21:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-04 21:35 [PATCH 0/3] e2fsprogs: Adding itree feature/inode flags Radek Pazdera
2013-05-04 21:35 ` Radek Pazdera [this message]
2013-05-04 21:35 ` [PATCH 2/3] libext2fs: Adding inode flag for itree Radek Pazdera
2013-05-04 21:35 ` [PATCH 3/3] mke2fs, tune2fs: Adding support for the itree flag Radek Pazdera
2013-05-05 3:24 ` [PATCH 0/3] e2fsprogs: Adding itree feature/inode flags Andreas Dilger
2013-05-07 12:47 ` Radek Pazdera
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=1367703310-3842-2-git-send-email-rpazdera@redhat.com \
--to=rpazdera@redhat.com \
--cc=kasparek@fit.vutbr.cz \
--cc=lczerner@redhat.com \
--cc=linux-ext4@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).