On Wed, Apr 02, 2008 at 02:25:10PM -0700, Anirban Sinha wrote: > >As you can see, we have an extra u_ptr member in the union (which is > the > >same as in the kernel: include/linux/nfsd/syscall.h). > > > >For experiment, I removed this member, recompiled nfs-utils and wala! > >The kernel now gets the correct value of the server thread #. > > > >I am a bit puzzled by this since u_umap member already has a char* and > I > >think adding a void* does not change the alignment of the union. > > > Indeed. Actually, by mistake, I was using the new 1.1.2 nfs-utils > binaries and making changes in the old 1.1.0 nfs-utils source. The > removal of the member does not change anything. What is happening is > that an upgrade to the new 1.1.2 nfs-utils binaries solves the problem. > I think you can reproduce the problem at your end simply by unmounting > nfsd filesystem and using 1.1.0 nfs-utils binary. OK! Hm, do you know which patch actually fixed this? (Is it actually just the same problem you reported before?) On a quick skim through the git history I'm not seeing it. --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
