linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wouter Batelaan <wouter.batelaan@nxp.com>
To: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: mismatch between 2.6.19 and nfs-utils-1.0.10 nfsctl_arg structure???
Date: Wed, 21 Feb 2007 15:46:06 +0000	[thread overview]
Message-ID: <45DC693E.2010805@nxp.com> (raw)
In-Reply-To: <45DB3871.5070604@nxp.com>

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

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;

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 :-(

Wouter Batelaan



  parent reply	other threads:[~2007-02-21 15:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-20 18:05 mismatch between 2.6.19 and nfs-utils-1.0.10 nfsctl_arg structure??? Wouter Batelaan
2007-02-21  0:04 ` Neil Brown
2007-02-21 15:46 ` Wouter Batelaan [this message]
2007-02-21 20:03   ` Neil Brown
2007-02-23 15:25 ` Wouter Batelaan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=45DC693E.2010805@nxp.com \
    --to=wouter.batelaan@nxp.com \
    --cc=linux-fsdevel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).