The code 0x0080 seems to be reserved for EXT4_FEATURE_RO_COMPAT_HAS_SNAPSHOT in e2fsprogs/lib/ext2fs/ext2_fs.h for Next3 snapshot feature. Thanks, -- Aditya On Mon, Feb 14, 2011 at 6:04 PM, Tao Ma <tm@xxxxxx> wrote: > Hi Aditya, > On 02/15/2011 09:06 AM, Aditya Kali wrote: >> >> I am working on patch to add quota as a built-in feature for ext4 >> filesystem. The implementation is based on the design given at >> https://ext4.wiki.kernel.org/index.php/Design_For_1st_Class_Quota_in_Ext4. >> This patch reserves the inode numbers 3 and 4 for quota purposes and >> also reserves EXT4_FEATURE_RO_COMPAT_QUOTA feature code. >> >> Signed-off-by: Aditya Kali<adityakali@xxxxxxxxxx> >> --- >> Âfs/ext4/ext4.h |  Â3 +++ >> Â1 files changed, 3 insertions(+), 0 deletions(-) >> >> diff --git a/fs/ext4/ext4.h b/fs/ext4/ext4.h >> index 0c8d97b..127f76f 100644 >> --- a/fs/ext4/ext4.h >> +++ b/fs/ext4/ext4.h >> @@ -209,6 +209,8 @@ struct ext4_io_submit { >>  */ >> Â#define    EXT4_BAD_INO       1   Â/* Bad blocks inode */ >> Â#define EXT4_ROOT_INO     Â2   Â/* Root inode */ >> +#define EXT4_USR_QUOTA_INO   Â3   Â/* User quota inode */ >> +#define EXT4_GRP_QUOTA_INO   Â4   Â/* Group quota inode */ >> Â#define EXT4_BOOT_LOADER_INO  5   Â/* Boot loader inode */ >> Â#define EXT4_UNDEL_DIR_INO   6   Â/* Undelete directory inode */ >> Â#define EXT4_RESIZE_INO        Â7   Â/* Reserved group >> descriptors inode */ >> @@ -1337,6 +1339,7 @@ static inline void ext4_clear_state_flags(struct >> ext4_inode_info *ei) >> Â#define EXT4_FEATURE_RO_COMPAT_GDT_CSUM        0x0010 >> Â#define EXT4_FEATURE_RO_COMPAT_DIR_NLINK   Â0x0020 >> Â#define EXT4_FEATURE_RO_COMPAT_EXTRA_ISIZE  Â0x0040 >> +#define EXT4_FEATURE_RO_COMPAT_QUOTA      0x0100 >> > > I am just wondering why 0x0080 is skipped here? It is reserved already? >> >> Â#define EXT4_FEATURE_INCOMPAT_COMPRESSION   0x0001 >> Â#define EXT4_FEATURE_INCOMPAT_FILETYPE        Â0x0002 >> > > Regards, > Tao > -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html