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, ** Tags removed: kernel-unable-to-test-upstream ** Tags added: kernel-bug-exists-upstream ** Tags added: raring -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1101292 Title: NFSv4 regression in 3.4-rc1 causes Invalid Argument on chown/grp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1101292/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
