From: Paul Collins <paul@burly.ondioline.org>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: linux-kernel@vger.kernel.org, nfsv4@linux-nfs.org,
linuxppc-dev@ozlabs.org, Neil Brown <neilb@suse.de>
Subject: Re: nfsd, v4: oops in find_acceptable_alias, ppc32 Linux, post-2.6.27-rc1
Date: Sun, 03 Aug 2008 10:36:51 +1200 [thread overview]
Message-ID: <87abfvm4cc.fsf@burly.wgtn.ondioline.org> (raw)
In-Reply-To: <20080802184554.GB715@fieldses.org> (J. Bruce Fields's message of "Sat, 2 Aug 2008 14:45:54 -0400")
"J. Bruce Fields" <bfields@fieldses.org> writes:
> On Sun, Aug 03, 2008 at 12:03:18AM +1200, Paul Collins wrote:
>> I just got the oops below on a ppc32 NFS4 server. I was cross-compiling
>> Linux with an amd64 client at the time. The server is running Linus's
>> tree as of 94ad374a0751f40d25e22e036c37f7263569d24c, the client is
>> running 2.6.26.
>>
>> The server's kernel was cross-compiled with gcc 4.2.4-3 and binutils
>> 2.18.50.20080610-1, both built from the Debian sources following their
>> toolchain-building procedures.
>
> Without having really thought about this,
>
> 496d6c32d4d057cb44272d9bd587ff97d023ee92 "nfsd: fix spurious
> EACCESS in reconnect_path()"
>
> is one suspect; it might be worth checking whether the problem's
> reproduceable with that reverted. But I assume we're not so lucky as to
> have a 100% reproduceable problem here?
Unknown. I've kicked off a fresh build. Here's hoping!
> What do your export options look like?
$ cat /etc/exports
/srv/nfsv4 *(sec=krb5:krb5i:krb5p,rw,fsid=0,crossmnt,insecure,no_subtree_check)
/srv/nfsv4/home/paul *(sec=krb5:krb5i:krb5p,rw,insecure,no_subtree_check)
$ mount | grep bind
/home/paul on /srv/nfsv4/home/paul type none (rw,bind)
--
Paul Collins
Wellington, New Zealand
Dag vijandelijk luchtschip de huismeester is dood
next prev parent reply other threads:[~2008-08-02 22:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-02 12:03 Paul Collins
2008-08-02 18:45 ` J. Bruce Fields
2008-08-02 22:36 ` Paul Collins [this message]
2008-08-03 6:47 ` Paul Collins
2008-08-03 12:09 ` Neil Brown
2008-08-03 12:25 ` Paul Collins
2008-08-04 4:08 ` Neil Brown
2008-08-04 5:11 ` Paul Collins
2008-08-04 10:00 ` Paul Collins
2008-08-04 14:36 ` Michael Ellerman
2008-08-04 20:51 ` Paul Collins
2008-08-04 20:59 ` J. Bruce Fields
2008-08-05 0:16 ` Michael Ellerman
2008-08-05 3:43 ` Paul Collins
2008-08-05 4:34 ` Michael Ellerman
2008-08-05 4:47 ` Paul Collins
2008-08-05 7:16 ` Benjamin Herrenschmidt
2008-08-06 6:29 ` Benjamin Herrenschmidt
2008-08-25 20:12 ` Bill Davidsen
2008-08-05 9:43 ` Paul Collins
2008-08-05 11:53 ` Michael Ellerman
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=87abfvm4cc.fsf@burly.wgtn.ondioline.org \
--to=paul@burly.ondioline.org \
--cc=bfields@fieldses.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=neilb@suse.de \
--cc=nfsv4@linux-nfs.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
all inboxes | Powered by JetHome®