Comment 6 for bug 1101292

I have verified this null-termination occurs in quantal even with a precise nfsv4 server with no security set. I have also verified that this is still the same in raring, and appears to be be maintained in upstream. I read through the RFC, and it does not appear to be incorrect in reference to the protocol *(as far as I read it). Still I sent an e-mail to linux-nfs mailing list to have upstream maintainers take a look at it.

Until I get a response from the upstream maintainers, I believe that it is actually allowed to null-terminate the string like this. As a result, I think the fix will have to be done in the AIX server.

Just in case Rolf Anders, can you please attach a tcpdump of a single run of chown or chgrp?

Thank you,