linux-ext4 - Reserved GDT inode: blocks vs extents

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]

Message-ID: <BAY406-EAS150EB9E4098E2894ADA30B7FDB40@phx.gbl>
Date:	Fri, 19 Sep 2014 11:54:39 -0400
From:	TR Reardon <thomas_reardon@...mail.com>
To:	linux-ext4@...r.kernel.org
Subject: Reserved GDT inode: blocks vs extents

Hello all: there's probably a good reason for this, but I'm wondering why inode#7 (reserved GDT blocks) is always created with a block map rather than extent? 

 [see ext2fs_create_resize_inode()]

Would changing this to extent resolve problem of resize_inode and 64bit / >16TB filesystems?