On Fri, Jun 21, 2013 at 10:32:22AM +0200, Sven Geggus wrote: > J. Bruce Fields schrieb am Donnerstag, den 20. Juni um 16:52 Uhr: > > > What happens with NFSv3? > > I have no Idea. I have a NFS4-only Server Setup and would need to enable v3 > explicitly. > > > So it looks it did a null init_sec_context establishment and then the > > server didn't reply to the first rpc call using the new context. But > > it's hard to be sure without more details--could I get the binary dump? > > Attached (Server kernel was 3.10.0-rc2 with patch below). OK, yes, thanks, the init_sec_context exchange does look acceptable but the server never responds to the first real rpc (a SETCLIENTID) using the new context. Could you run strace -p $(pidof rpc.svcgssd) -s4096 -e trace=open,close,read,write on the server while trying this? That should capture the contents of the relevant upcalls. I wonder if there's something odd about the context svcgssd is passing down. > > Hm, or I wonder if 8b5309d41751b8a086d8e7a43abe37d9ff24559d "svcrpc: fix > > failures to handle -1 uid's and gid's" (appended) would help. > > No! I just patched this into a vanilla 3.10.0-rc2. Same Problem. The NFS-mount > just hangs. OK, thanks for checking. --b. -- 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
