linux-ext4 - Re: htree indexing and 64-bit file systems

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]

Date:	Sat, 07 Feb 2009 14:06:56 +0100
From:	Goswin von Brederlow <goswin-v-b@....de>
To:	linux-ext4@...r.kernel.org
Subject: Re: htree indexing and 64-bit file systems

Theodore Tso <tytso@....edu> writes:

> On Tue, Feb 03, 2009 at 05:22:02PM -0500, Valerie Aurora Henson wrote:
>> I've just been ignoring htree indexing for now, but the regression
>> failure in Ted's rebased 64bit tree looks suspiciously htree-related.
>> 
>> What's the interaction between htree and 64 bit file systems?  What
>> needs to change, if anything?
>
> There shouldn't be any.  The block numbers used in htree are logical
> block numbers (i.e., block 0 is the first block in the directory,
> block 1 is the 2nd block i the directory, etc.)
>
> 						- Ted

What if the directory is REALLY HUGE? :) Say >68.719.476.736 files.

Can ext4 64bit have directories >8TiB?

MfG
        Goswin
--
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