public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@redhat.com>
To: Chris Vine <chris-TF6qbakwsgc2epGFuHBODCp2UmYkHbXO@public.gmane.org>
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 11:11:32 -0400	[thread overview]
Message-ID: <20100618111132.20fb518a@corrin.poochiereds.net> (raw)
In-Reply-To: <20100618160411.14d65b2b-PlFwYbz7hoIyinQH9hAyzg@public.gmane.org>

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.

-- 
Jeff Layton <jlayton@redhat.com>

  parent reply	other threads:[~2010-06-18 15:09 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 [this message]
     [not found]               ` <20100618111132.20fb518a-4QP7MXygkU+dMjc06nkz3ljfA9RmPOcC@public.gmane.org>
2010-06-18 22:45                 ` Chris Vine

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=20100618111132.20fb518a@corrin.poochiereds.net \
    --to=jlayton@redhat.com \
    --cc=bfields@fieldses.org \
    --cc=chris-TF6qbakwsgc2epGFuHBODCp2UmYkHbXO@public.gmane.org \
    --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