linux-ext4 - Re: Question about e2fsck and HTree

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:	Fri, 23 Apr 2010 20:45:44 -0400
From:	tytso@....edu
To:	Evgeniy Ivanov <lolkaantimat@...il.com>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: Question about e2fsck and HTree

On Thu, Apr 22, 2010 at 11:43:30PM +0400, Evgeniy Ivanov wrote:
> Hello,
> 
> I have a question about ext2/ext3.
> 
> As I understand directory indexing is compatible feature, currently my
> implementations doesn't support HTree.
> I do some things (make kernel and libs) with FS and check it with
> e2fsck: it creates index (everything else is ok, exit status is 1).
> Then I do same things with FS and check again:
> 
> HTree directory inode 23316 has an invalid root node.
> 
> Is it OK for implementation without directory indexing?

If your implementation of extN don't support HTree, then it's
important that when you modify a filesystem you clear the inode's
EXT2_INDEX_FL flag.   Then the right thing will happen....

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