From: Chris Vine <chris-TF6qbakwsgc2epGFuHBODCp2UmYkHbXO@public.gmane.org>
To: Jeff Layton <jlayton@redhat.com>
Cc: bfields@fieldses.org, linux-nfs@vger.kernel.org
Subject: Re: [PATCH] nfsd: just keep single lockd reference for nfsd
Date: Fri, 18 Jun 2010 23:45:40 +0100 [thread overview]
Message-ID: <20100618234540.64e7b605@boulder.homenet> (raw)
In-Reply-To: <20100618111132.20fb518a-4QP7MXygkU+dMjc06nkz3ljfA9RmPOcC@public.gmane.org>
On Fri, 18 Jun 2010 11:11:32 -0400
Jeff Layton <jlayton@redhat.com> wrote:
> On Fri, 18 Jun 2010 16:04:11 +0100
> Chris Vine <chris-TF6qbakwsgc2epGFuHBODCp2UmYkHbXO@public.gmane.org> wrote:
>
> > On Fri, 18 Jun 2010 10:30:42 -0400
> > Jeff Layton <jlayton@redhat.com> wrote:
> > [snip]
> > > Thanks for testing them. No oops == improvement!
> > >
> > > ...but it would still be good to know what's wrong here. It sounds
> > > like something is really odd with loopback communications on this
> > > box. Is the ipv4 loopback interface up at this time? Do you have
> > > any iptables stuff set up that might be filtering out portmap
> > > registration requests from the kernel? What happens if you run
> > > "rpcinfo"? Does it also hang?
> > >
> > > The kernel uses TCP for talking to portmap these days, so it might
> > > also be good to see whether you can use rpcinfo to talk to it with
> > > TCP too...
> >
> > You are right. Although the lo interface is up, localhost is broken
> > in 2.6.35-rc3. External networking works OK which is why I hadn't
> > noticed.
> >
> > It looks like some other unrelated bug in 2.6.35 is at work. Quite
> > why it doesn't strike my Pentium machine I can't say. The netbook
> > takes its network address from DHCP (my Pentium does not) but that
> > shouldn't make any difference to localhost.
> >
> > I shall do a bit more looking around later today or tomorrow.
> >
> > Chris
> >
> >
>
> Ok, good to know. I'll still plan to pursue these fixes. The error
> handling in nfsd obviously an area that needs improvement. I think
> Bruce's current plan is to take the earlier patches in that stack for
> 2.6.36. If this one is OK, it's probably reasonable to go in at the
> same time.
The problem is indeed a loopback bug and for anyone else suffering this
with nfsd, the fix is a one liner, here:
http://marc.info/?l=linux-kernel&m=127646140827821
At least this had the benefit of improving the error handling of nfsd!
Chris
prev parent reply other threads:[~2010-06-18 22:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-18 11:02 [PATCH] nfsd: just keep single lockd reference for nfsd Jeff Layton
2010-06-18 14:18 ` Chris Vine
[not found] ` <20100618151808.6e40a0ca-PlFwYbz7hoIyinQH9hAyzg@public.gmane.org>
2010-06-18 14:30 ` Jeff Layton
[not found] ` <20100618103042.080aa597-4QP7MXygkU+dMjc06nkz3ljfA9RmPOcC@public.gmane.org>
2010-06-18 15:04 ` Chris Vine
[not found] ` <20100618160411.14d65b2b-PlFwYbz7hoIyinQH9hAyzg@public.gmane.org>
2010-06-18 15:11 ` Jeff Layton
[not found] ` <20100618111132.20fb518a-4QP7MXygkU+dMjc06nkz3ljfA9RmPOcC@public.gmane.org>
2010-06-18 22:45 ` Chris Vine [this message]
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=20100618234540.64e7b605@boulder.homenet \
--to=chris-tf6qbakwsgc2epgfuhbodcp2umykhbxo@public.gmane.org \
--cc=bfields@fieldses.org \
--cc=jlayton@redhat.com \
--cc=linux-nfs@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