linux-ext4 - [Bug 196405] mkdir mishandles st_nlink in ext4 directory with 64997 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] [thread-next>] [day] [month] [year] [list]

Message-ID: <bug-196405-13602-AfTk7lpbDT@https.bugzilla.kernel.org/>
Date:   Tue, 18 Jul 2017 21:54:52 +0000
From:   bugzilla-daemon@...zilla.kernel.org
To:     linux-ext4@...nel.org
Subject: [Bug 196405] mkdir mishandles st_nlink in ext4 directory with 64997
 subdirectories

https://bugzilla.kernel.org/show_bug.cgi?id=196405

--- Comment #4 from Andreas Dilger (adilger.kernelbugzilla@...ger.ca) ---
The limit is implemented as < 65000, which was somewhat below the hard limit of
the ext4_inode.i_links_count __u16 field of 65535.  There is no hard reason for
65000 except to allow some margin for detecting overflow, and reserved values
if there was a need.  I don't think it makes a big practical difference whether
directory link counts are accurate up to 65000 or 65534 subdirectories, since
very few systems have this many subdirectories.

In theory, we could add an i_links_count_hi field to extend this to a 32-bit
value, but it isn't clear if there is a big benefit from doing this?

-- 
You are receiving this mail because:
You are watching the assignee of the bug.