Messages in this thread | | | Subject | Re: [Ext2-devel] Re: [NFS] htree+NFS (NFS client bug?) | From | Trond Myklebust <> | Date | 27 Nov 2002 23:44:01 +0100 |
| |
>>>>> " " == Stephen C Tweedie <sct@redhat.com> writes:
>> If glibc issued a new readdir request (which is what I suspect >> has happened here), the NFS client has no idea what the >> previous reply was
> Well, glibc will *always* issue another readdir, because the > only way we can ever tell glibc that we're at EOF on the > directory is when we eventually return 0 from getdents. The > question about client behaviour is, if we've already been told > that the stream is at EOF, should the client simply discard > that info and keep reading regardless, or should it cache the > EOF status?
We could possibly cache the EOF status by overloading some other field in the struct file. f_version comes to mind as a useful candidate, since it automatically gets reset by llseek.
Cheers, Trond - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |