linux-ext4 - Re: [Patch 6/13] Allow more than 32000 subdirectories

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-prev] [day] [month] [year] [list]

Date:	Sat, 4 Aug 2007 10:47:21 -0600
From:	Andreas Dilger <adilger@...sterfs.com>
To:	Theodore Tso <tytso@....edu>
Cc:	Girish Shilamkar <girish@...sterfs.com>,
	Ext4 Mailing List <linux-ext4@...r.kernel.org>
Subject: Re: [Patch 6/13]  Allow more than 32000 subdirectories

On Aug 04, 2007  09:51 -0400, Theodore Tso wrote:
> On Tue, Jul 24, 2007 at 04:34:56PM +0530, Girish Shilamkar wrote:
> > This patch includes the changes required to e2fsck to understand the 
> > nlink count changes made in the kernel. In pass2, while counting the 
> > links for a directory, if the link count exceeds 65000, its permanently 
> > set to EXT2_NLINK_MAXED (EXT2_LINK_MAX + 100). In pass4, when the 
> > counted and actual nlink counts are compared, e2fsck does not flag 
> > an error if counted links = EXT2_NLINK_MAXED and existing link count is 1. 
> 
> Has this actually been implemented in the kernel?  I don't think I've
> seen a patch which implements the a large number file links.  The
> 65000 subdir patch does *not* define EXT2_NLINK_MAXED, nor does this
> patch.   And this patch seems to use EXT2_LINK_MAX + 10, not +100.

I haven't tested hard-linked files myself, but they should remain with
a limit of EXT2_LINK_MAX.  It is only for directories that the link
count can be exceeded.  We have definitely tested with > 65000 subdirs.

Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.

-
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