Hi, we hit some strange behavior which is expected from one side, but unexpected at the same time. We run our nfs server with v3 and v4. Due to misconfiguration in idmapping, we got some files to be owned by uid -1. Which is ok, as with v4 server returns nobody. Nevertheless, this prevent to list the directory with v3. This is the result of uid_valid()/gid_valid() calls in nfs3xdr.c:decode_fattr3. The uid_valid/gid_valid checks that provided uid/gid are not -1. Probably this is ok. My confusion is: a) one file with bad uid/gid prevents listing of a directory, b) in nfs v3 spec uid3 (as well as uid_t in linux) is unsigned int 32 and value 0xffffffff is absolutely valid. Tigran. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
