Which is of course, not a good assumption since the RFC defines v2 cookies
as opaque. (v3 cookies are said to be an unsigned 64 bit integer, but still
does not state what, if any assumptions may be made on the value.)
(And at least one program, cfs, just ships it's internal cookie value out,
the kernel then tries to ntohl it and gets a now non-increasing, basically
random value, which breaks the caching and loses hoardes of directory
entries. However since internally cfs uses an increasing value, this is easy
to solve.)
I'm not sure what other NFS implementations may have problems like this, I
suspect it's not a problem for 'normal' implementations, but may crop up
here and there.
-Steve Wormley
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/