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

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

Message-ID: <bug-196405-13602-PRWmiANPzS@https.bugzilla.kernel.org/>
Date:   Sat, 22 Jul 2017 14:41:47 +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 #22 from Theodore Tso (tytso@....edu) ---
Right, the fact that the two bugs that Michael cited was about the st_nlinks
being "wrong" is in fact a good thing.  Paul is asserting that there is vast
amount of breakage because ext4 can return an st_nlinks value of 1 on a
directory, to the extent that he believes we should withdrawing the dir_nlinks
feature.   My argument is if we've lived with this for ten years without users
screaming about things being broken, then we're probably ok and we should fix
this by changing the documentation.   Paul then responded by pointing out the
bugs.  But if the bugs are about st_nlinks being "wrong" causing users to be
confused, and not about real life use cases breaking, then I'm going to be much
less concerned.

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