From: Wouter Batelaan <wouter.batelaan@nxp.com>
To: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: mismatch between 2.6.19 and nfs-utils-1.0.10 nfsctl_arg structure???
Date: Tue, 20 Feb 2007 18:05:37 +0000 [thread overview]
Message-ID: <45DB3871.5070604@nxp.com> (raw)
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
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.
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;
next reply other threads:[~2007-02-20 18:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-20 18:05 Wouter Batelaan [this message]
2007-02-21 0:04 ` mismatch between 2.6.19 and nfs-utils-1.0.10 nfsctl_arg structure??? Neil Brown
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=45DB3871.5070604@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.