linux-ext4 - 64-bit inode support in e2fsprogs? (was Re: [RFC PATCH 11/17] Fix overflow in calculation of total file system blocks)

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20081114031028.GH20637@shell>
Date:	Thu, 13 Nov 2008 22:10:28 -0500
From:	Valerie Aurora Henson <vaurora@...hat.com>
To:	Andreas Dilger <adilger@....com>
Cc:	linux-ext4@...r.kernel.org, Theodore Tso <tytso@....edu>
Subject: 64-bit inode support in e2fsprogs? (was Re: [RFC PATCH 11/17] Fix overflow in calculation of total file system blocks)

On Thu, Nov 13, 2008 at 01:04:02PM -0700, Andreas Dilger wrote:
> 
> There is a similar fix missing from ext2fs_allocate_inode_bitmap() (even
> though there isn't any support for 64-bit inode numbers as yet.

That's a question I have: Should the 64-bit port have partial support
for 64-bit inodes?  Supporting 64-bit inodes is enough effort and risk
(especially in terms of glue code to convert back to 32-bit versions)
that I think it makes sense to wait until we know more about what they
will look like and have concrete plans to support them.

-VAL
--
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