Re: mismatch between 2.6.19 and nfs-utils-1.0.10 nfsctl_arg structure???

[Neil Brown <neilb@suse.de>]

On Wednesday February 21, wouter.batelaan@nxp.com wrote:
> linux-fsdevel-owner@vger.kernel.org wrote on 2007-02-21 00:04:40:
> 
>  > You will need patch f988443a84528bd30c2f474efa5e2c511959f19b [1]
>  > or run
>  >    mount -t nfsd nfsd /proc/fs/nfs/nfsd
>  > before starting mountd.
> 
> I applied the patch, and attempted the mount cmd above.
> I assume you mistyped the directory path, because
> /proc/fs/nfs/nfsd does not exist, so I used /proc/fs/nfsd

Sorry, yes.  You chose the right path.

> 
> Unfortunately it has not made any difference.
> 
>  > The differences are not significant.
> 
> Really? Surely if userspace uses this order
> 
>  > >       struct nfsctl_uidmap   u_umap;
>  > >       struct nfsctl_fhparm   u_getfh;
>  > >       struct nfsctl_fdparm   u_getfd;
>  > >       struct nfsctl_fsparm   u_getfs;
> 
> but kernelspace expects this
>  > >       struct nfsctl_fdparm   u_getfd;
>  > >       struct nfsctl_fsparm   u_getfs;

They are inside a 'union'  Order is unimportant.

> 
> then we have significant differences?
> But if you're sure, then what else can be wrong?
> My /etc/exports file contains (adding all 'unsafe' options I can find):
> 
> /p 
> (rw,sync,no_root_squash,no_subtree_check,crossmnt,insecure,nohide,insecure_locks,no_acl)
> 
> I tried with and without (empty) hosts.allow and hosts.deny files.
> 
> I'm running out of ideas :-(

Run
  strace -o /tmp/strace -s 1000 -p `pidof mountd`
on the server, then attempt the mount on the client.
Then interrupt the 'strace' and send me "/tmp/trace".

NeilBrown