On Mon, Jan 07, 2002 at 12:28:54PM -0600, Dave Kleikamp wrote:
> Christian,
> Thanks for the in-depth analysis. I'm not familiar with the NFS code,
> so I'm confused about how it is handling the "cookies". As JFS returns
> the entries via "filldir", each entry's position is correctly returned.
> But when we have exhausted all entries, f_pos is set to -1. I don't
> know why NFS would associate this with the last returned entry, since I
> understand it to be associated with the next entry which would be
> returned in a subsequent call to readdir.
>
> Would you happen to know if -1 is special? Would returning -2 make
> things work, or does it really need to be a positive number?
NFSv2 doesn't support 64 bit file offset, the file fs/nfsd/nfsxdr.c
contains the follwoing code in nfssvc_encode_entry():
if (offset > ~((u32) 0))
return -EINVAL;
[line 402/403 for kernel 2.4.17]
As (u64)((loff_t)-1) > ~((u32)0) we get -EINVAL..
Christoph
--
Of course it doesn't work. We've performed a software upgrade.
_______________________________________________
Jfs-discussion mailing list
[EMAIL PROTECTED]
http://www-124.ibm.com/developerworks/oss/mailman/listinfo/jfs-discussion
