linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: Wouter Batelaan <wouter.batelaan@nxp.com>
Cc: "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 11:04:40 +1100	[thread overview]
Message-ID: <17883.35992.171351.381438@notabene.brown> (raw)
In-Reply-To: message from Wouter Batelaan on Tuesday February 20

On Tuesday February 20, wouter.batelaan@nxp.com wrote:
> Hi,
> 
> I'm trying to get an nfs server setup on our embedded 2.6.19 kernel 
> system. I've chosen to use the kernel nfsd module,
> and am using the latest nfs-utils.
> It all starts running, but I get this:
>      mount -t nfs 127.0.0.1:/etc /tmp/try
> mount: 127.0.0.1:/etc failed, reason given by server: Permission denied
> mount: nfsmount failed: Bad file descriptor
> mount: Mounting 127.0.0.1:/etc on /tmp/try failed: Bad file descriptor
> 
> Having added a bit of debugging /var/log/messages shows this:
> daemon.warn mountd[545]: getfh.c:73: getfh_size (/etc)
> daemon.warn mountd[545]: nfsctl.c:26: syscall nfsctl
> daemon.warn mountd[545]: nfsctl.c:28: syscall nfsctl => -1
> daemon.warn mountd[545]: getfh failed: Operation not permitted

You will need patch f988443a84528bd30c2f474efa5e2c511959f19b [1]
or run
   mount -t nfsd nfsd /proc/fs/nfs/nfsd
before starting mountd.


> 
> Looking in detail at the syscall made, I see that the structure
> definition for nfsctl_arg is different between kernel and nfs-utils.
> 
> Huh? What am I missing here? Any pointers appreciated.
> Wouter.

The differences are not significant.

NeilBrown

[1] http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=f988443a84528bd30c2f474efa5e2c511959f19b


> 
> Kernel 2.6.19.1: include/linux/nfsd/syscall.h:
> struct nfsctl_arg {
> 	int			ca_version;	/* safeguard */
> 	union {
> 		struct nfsctl_svc	u_svc;
> 		struct nfsctl_client	u_client;
> 		struct nfsctl_export	u_export;
> 		struct nfsctl_fdparm	u_getfd;
> 		struct nfsctl_fsparm	u_getfs;
>                  <snip>
> 		void *u_ptr;
> 	} u;
> 
> 
> nfs-utils 1.0.10: support/include/nfs/nfs.h:
> struct nfsctl_arg {
> 	int			ca_version;	/* safeguard */
> 	union {
> 		struct nfsctl_svc	u_svc;
> 		struct nfsctl_client	u_client;
> 		struct nfsctl_export	u_export;
> 		struct nfsctl_uidmap	u_umap;
> 		struct nfsctl_fhparm	u_getfh;
> 		struct nfsctl_fdparm	u_getfd;
> 		struct nfsctl_fsparm	u_getfs;
> 	} u;
> 
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2007-02-21  0:05 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 [this message]
2007-02-21 15:46 ` Wouter Batelaan
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=17883.35992.171351.381438@notabene.brown \
    --to=neilb@suse.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=wouter.batelaan@nxp.com \
    /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).