From: Ralf Baechle <ralf@linux-mips.org>
To: Kaz Kylheku <kaz@zeugmasystems.com>
Cc: linux-mips@linux-mips.org
Subject: Re: "exportfs -a" -> stale NFS filehandle
Date: Thu, 15 Nov 2007 23:02:19 +0000 [thread overview]
Message-ID: <20071115230218.GA1696@linux-mips.org> (raw)
In-Reply-To: <DDFD17CC94A9BD49A82147DDF7D545C54DC8F6@exchange.ZeugmaSystems.local>
On Thu, Nov 15, 2007 at 12:15:39PM -0800, Kaz Kylheku wrote:
> Ralf Baechle wrote:
> > On Thu, Nov 15, 2007 at 11:26:06AM -0800, Kaz Kylheku wrote:
> >
> >> After backing out the nfsutils patch, the diskless node does boot.
> >>
> >> However, the original "exportfs -a" problem comes back!
> >>
> >> So this problem is not resolved simply by using the correct compat
> >> routine; it's deeper.
> >>
> >> Sigh.
> >
> > Thanks for testing anyway!
>
> I'm continuing to dig into the problem.
>
> The export logic doesn't even go through nfsctl() anyway, which is why I
> originally hadn't even suspected that syscall.
>
> The nfsexport() function in nfsutils first tries opening
> "/proc/net/rpc/nfsd.fh./channel". If that works, it uses that, via a
> text-based protocol. Only if that interface doesn't exist does it fall
> back on the nfsctl(NFSCTL_EXPORT, ...) interface.
After checking that latest glibc still isn't trying to compensate for the
N32 nfsservctl issue in userland I've applied the patch I sent you earlier.
Ralf
next prev parent reply other threads:[~2007-11-15 23:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-14 23:19 "exportfs -a" -> stale NFS filehandle Kaz Kylheku
2007-11-14 23:19 ` Kaz Kylheku
2007-11-15 0:48 ` Ralf Baechle
2007-11-15 18:38 ` Kaz Kylheku
2007-11-15 18:38 ` Kaz Kylheku
2007-11-15 19:26 ` Kaz Kylheku
2007-11-15 19:26 ` Kaz Kylheku
2007-11-15 19:45 ` Ralf Baechle
2007-11-15 20:15 ` Kaz Kylheku
2007-11-15 20:15 ` Kaz Kylheku
2007-11-15 23:02 ` Ralf Baechle [this message]
2007-11-19 22:26 ` Kaz Kylheku
2007-11-19 22:26 ` Kaz Kylheku
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=20071115230218.GA1696@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=kaz@zeugmasystems.com \
--cc=linux-mips@linux-mips.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.