From: Qi Yong <qiyong@fc-cn.com>
To: akpm@osdl.org
Cc: sct@redhat.com, adilger@clusterfs.com,
ext2-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: [patch] ext3: remove btree_dir
Date: Thu, 13 Jul 2006 16:05:38 +0800 [thread overview]
Message-ID: <20060713080538.GA20259@localhost.localdomain> (raw)
Remove support for EXT3_FEATURE_RO_COMPAT_BTREE_DIR, so mount can
safely fail out when some new feature added using 0x0004.
Signed-off-by: Qi Yong <qiyong@fc-cn.com>
---
diff --git a/include/linux/ext2_fs.h b/include/linux/ext2_fs.h
index facf34e..d63d2ec 100644
--- a/include/linux/ext2_fs.h
+++ b/include/linux/ext2_fs.h
@@ -463,7 +463,6 @@ #define EXT2_FEATURE_COMPAT_ANY 0xffff
#define EXT2_FEATURE_RO_COMPAT_SPARSE_SUPER 0x0001
#define EXT2_FEATURE_RO_COMPAT_LARGE_FILE 0x0002
-#define EXT2_FEATURE_RO_COMPAT_BTREE_DIR 0x0004
#define EXT2_FEATURE_RO_COMPAT_ANY 0xffffffff
#define EXT2_FEATURE_INCOMPAT_COMPRESSION 0x0001
@@ -477,8 +476,7 @@ #define EXT2_FEATURE_COMPAT_SUPP EXT2_FE
#define EXT2_FEATURE_INCOMPAT_SUPP (EXT2_FEATURE_INCOMPAT_FILETYPE| \
EXT2_FEATURE_INCOMPAT_META_BG)
#define EXT2_FEATURE_RO_COMPAT_SUPP (EXT2_FEATURE_RO_COMPAT_SPARSE_SUPER| \
- EXT2_FEATURE_RO_COMPAT_LARGE_FILE| \
- EXT2_FEATURE_RO_COMPAT_BTREE_DIR)
+ EXT2_FEATURE_RO_COMPAT_LARGE_FILE)
#define EXT2_FEATURE_RO_COMPAT_UNSUPPORTED ~EXT2_FEATURE_RO_COMPAT_SUPP
#define EXT2_FEATURE_INCOMPAT_UNSUPPORTED ~EXT2_FEATURE_INCOMPAT_SUPP
diff --git a/include/linux/ext3_fs.h b/include/linux/ext3_fs.h
index 5607e64..7974c44 100644
--- a/include/linux/ext3_fs.h
+++ b/include/linux/ext3_fs.h
@@ -553,7 +553,6 @@ #define EXT3_FEATURE_COMPAT_DIR_INDEX 0
#define EXT3_FEATURE_RO_COMPAT_SPARSE_SUPER 0x0001
#define EXT3_FEATURE_RO_COMPAT_LARGE_FILE 0x0002
-#define EXT3_FEATURE_RO_COMPAT_BTREE_DIR 0x0004
#define EXT3_FEATURE_INCOMPAT_COMPRESSION 0x0001
#define EXT3_FEATURE_INCOMPAT_FILETYPE 0x0002
@@ -566,8 +565,7 @@ #define EXT3_FEATURE_INCOMPAT_SUPP (EXT3
EXT3_FEATURE_INCOMPAT_RECOVER| \
EXT3_FEATURE_INCOMPAT_META_BG)
#define EXT3_FEATURE_RO_COMPAT_SUPP (EXT3_FEATURE_RO_COMPAT_SPARSE_SUPER| \
- EXT3_FEATURE_RO_COMPAT_LARGE_FILE| \
- EXT3_FEATURE_RO_COMPAT_BTREE_DIR)
+ EXT3_FEATURE_RO_COMPAT_LARGE_FILE)
/*
* Default values for user and/or group using reserved blocks
--
Qi Yong
next reply other threads:[~2006-07-13 8:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-13 8:05 Qi Yong [this message]
2006-07-13 11:59 ` [patch] ext3: remove btree_dir Stephen C. Tweedie
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=20060713080538.GA20259@localhost.localdomain \
--to=qiyong@fc-cn.com \
--cc=adilger@clusterfs.com \
--cc=akpm@osdl.org \
--cc=ext2-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sct@redhat.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