From: Florian Weimer <email@example.com> To: "Theodore Y. Ts'o" <firstname.lastname@example.org> Cc: Rich Felker <email@example.com>, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org Subject: Re: [musl] getdents64 lost direntries with SMB/NFS and buffer size < unknown threshold Date: Wed, 25 Dec 2019 20:38:07 +0100 Message-ID: <email@example.com> (raw) In-Reply-To: <20191121175418.GI4262@mit.edu> (Theodore Y. Ts'o's message of "Thu, 21 Nov 2019 12:54:18 -0500") * Theodore Y. Ts'o: > On Wed, Nov 20, 2019 at 03:59:13PM -0500, Rich Felker wrote: >> >> POSIX only allows both behaviors (showing or not showing) the entry >> that was deleted. It does not allow deletion of one entry to cause >> other entries not to be seen. > > Agreed, but POSIX requires this of *readdir*. POSIX says nothing > about getdents64(2), which is Linux's internal implementation which is > exposed to a libc. Sure, but Linux better provides some reasonable foundation for a libc. I mean, sure, we can read the entire directory into RAM on the first readdir, and get a fully conforming implementation this way (and as Rich noted, glibc's 32 KiB buffer tends to approximate that in practice). But that doesn't strike me as particularly useful. The POSIX requirement is really unfortunate because it leads to incorrect implementations of rm -rf which would on a compliant system and fail in practice. > So we would need to see what is exactly going on at the interfaces > between the VFS and libc, the nfs client code and the VFS, the nfs > client code and the nfs server, and possibly the behavior of the nfs > server. > > First of all.... you can't reproduce this on anything other than with > NFS, correct? That is, does it show up if you are using ext4, xfs, > btrfs, etc.? I'm sure it shows up with certain directory contents on any Linux file system except for those that happen to have a separate B-tree (or equivalent) for telldir/seekdir support. And even those will have broken corner case in case of billions of directory operations. 32 bits are simply not enough storage space for the cookie. Hashing just masks the presence of these bugs, but does not eliminate them completely.
next prev parent reply index Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-11-20 0:15 Rich Felker 2019-11-20 19:57 ` [musl] " Florian Weimer 2019-11-20 20:59 ` Rich Felker 2019-11-21 17:54 ` Theodore Y. Ts'o 2019-12-25 19:38 ` Florian Weimer [this message] 2019-12-26 3:56 ` Theodore Y. Ts'o
Reply instructions: You may reply publically to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Linux-CIFS Archive on lore.kernel.org Archives are clonable: git clone --mirror https://lore.kernel.org/linux-cifs/0 linux-cifs/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 linux-cifs linux-cifs/ https://lore.kernel.org/linux-cifs \ email@example.com public-inbox-index linux-cifs Example config snippet for mirrors Newsgroup available over NNTP: nntp://nntp.lore.kernel.org/org.kernel.vger.linux-cifs AGPL code for this site: git clone https://public-inbox.org/public-inbox.git