>>>>> " " == Mogens Kjaer <mk@crc.dk> writes:

     > This turned out to be more difficult than I thought...

     > I suspect glibc-2.2-12 being the reason, but I'm not quite sure
     > yet:

     > The problem is, that the 64-bit dirent's are converted to
     > 32-bit dirent's and a sanity check is performed, if the inodes
     > or offsets don't fit into 32 bits.

     > The offset of the last entry is 4294967295 (no, not -1), this
     > won't fit in a signed 32 bit number.

     > Does this number come from the SGI or from the NFS stuff in the
     > Linux kernel?

It comes from the SGI. The NFS client just considers it all a cookie,
and passes it on to glibc. We probably shouldn't do that, as indeed
the cookie is not guaranteed to be 32-bit signed, but it's what we
always did for 2.2.x.

Cheers,
  Trond
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/