From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: David Howells <dhowells@redhat.com>
Cc: Linux Filesystem Development <linux-fsdevel@vger.kernel.org>,
Steve Dickson <SteveD@redhat.com>
Subject: Re: NFS4 mount problem
Date: Sun, 17 Apr 2005 15:33:35 -0400 [thread overview]
Message-ID: <1113766415.13680.79.camel@lade.trondhjem.org> (raw)
In-Reply-To: <17895.1113566268@redhat.com>
fr den 15.04.2005 Klokka 12:57 (+0100) skreiv David Howells:
> We've come across an interesting problem with NFS4 mount on a PPC64 box. If
> the mount program is compiled as PPC32, then the mount() syscall is returned
> EFAULT.
So, why is this not a case of "Doctor it hurts..."?
In exactly which case do people have absolutely no alternative but to
run a 32-bit version of the mount program on top of a kernel that was
compiled as PPC64?
A simple script that runs "uname -r" and switches a soft-link between
the 32-bit and 64-bit version of "mount" is not rocket science.
> I would prefer option (4), otherwise we have to find _all_ usages of the
> mount() system calls and fix them.
mount() is not a documented syscall. The binary formats for filesystems
like NFS are only documented inside the kernels to which they apply.
There should therefore be exactly ONE instance of usage, and that is in
the "mount" program itself.
Cheers,
Trond
--
Trond Myklebust <trond.myklebust@fys.uio.no>
next prev parent reply other threads:[~2005-04-17 19:33 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-15 11:57 NFS4 mount problem David Howells
2005-04-15 12:21 ` Stephen Rothwell
2005-04-15 19:51 ` Bryan Henderson
2005-04-15 20:22 ` David S. Miller
2005-04-15 22:07 ` Bryan Henderson
2005-04-17 13:55 ` Christoph Hellwig
2005-04-18 17:07 ` Bryan Henderson
2005-04-18 17:16 ` Al Viro
2005-04-18 17:33 ` David Howells
2005-04-18 17:43 ` Al Viro
2005-04-18 17:52 ` Bryan Henderson
2005-04-18 10:36 ` David Howells
2005-04-18 18:37 ` David S. Miller
2005-04-17 19:33 ` Trond Myklebust [this message]
2005-04-18 17:17 ` Bryan Henderson
2005-04-18 17:59 ` Trond Myklebust
2005-04-20 10:57 ` Andries Brouwer
2005-04-18 10:34 ` David Howells
2005-04-18 14:49 ` Trond Myklebust
2005-04-18 22:07 ` Bryan Henderson
2005-04-18 23:34 ` Trond Myklebust
2005-04-18 15:23 ` David Howells
2005-04-18 15:45 ` Trond Myklebust
2005-04-18 21:50 ` Bryan Henderson
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=1113766415.13680.79.camel@lade.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=SteveD@redhat.com \
--cc=dhowells@redhat.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).