linux-ext4 - [RFC] Add new extent structure in ext4

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 23 Jan 2012 20:51:53 +0800
From:	Robin Dong <hao.bigrat@...il.com>
To:	"Ted Ts'o" <tytso@....edu>, Andreas Dilger <adilger@...ger.ca>,
	Ext4 Developers List <linux-ext4@...r.kernel.org>
Subject: [RFC] Add new extent structure in ext4

Hi Ted, Andreas and the list,

After the bigalloc-feature is completed in ext4, we could have much more
big size of block-group (also bigger continuous space), but the extent
structure of files now limit the extent size below 128MB, which is not
optimal.

We could solve the problem by creating a new extent format to support
larger extent size, which looks like this:

struct ext4_extent2 {
	__le64	ee_block;	/* first logical block extent covers */
	__le64	ee_start;	        /* starting physical block */
	__le32	ee_len;		/* number of blocks covered by extent */
	__le32	ee_flags;	/* flags and future extension */
};

struct ext4_extent2_idx {
	__le64	ei_block;	        /* index covers logical blocks from 'block' */
	__le64	ei_leaf;	        /* pointer to the physical block of the next level */
	__le32	ei_flags;	        /* flags and future extension */
	__le32	ei_unused;	/* padding */
};

I think we could keep the structure of ext4_extent_header and add new
imcompat flag EXT4_FEATURE_INCOMPAT_EXTENTS2.

The new extent format could support 16TB continuous space and larger volumes.

What's your opinion?

-- 
--
Best Regard
Robin Dong
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html