From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: "Stephen R. van den Berg" <srb-PCMv+cxZuL0@public.gmane.org>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-nfs@vger.kernel.org
Subject: Re: Fw: Deadlock regression in v2.6.31.6
Date: Thu, 26 Nov 2009 10:20:59 -0500 [thread overview]
Message-ID: <1259248859.6715.50.camel@localhost> (raw)
In-Reply-To: <64b4daae0911260707i4064f608w4f7169441640567-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Thu, 2009-11-26 at 16:07 +0100, Stephen R. van den Berg wrote:
> On Thu, Nov 26, 2009 at 16:01, Trond Myklebust
> <trond.myklebust@fys.uio.no> wrote:
> > On Thu, 2009-11-26 at 00:11 +0100, Stephen R. van den Berg wrote:
> >> 1.2.3.167 is the Linux client kernel which locks up, 1.2.3.151 is the
> >> unfs server.
> >> It looks like the client terminates the TCP connection. The server
> >> confirms it, the client then sends a final acknowledge. At that point
> >> the client kernel locks up in the infinite loop.
>
> > OK. Have you tried running with RPCDBG_TRANS debugging enabled? I
> > suspect you might see a flood of 'sendmsg returned unrecognized error'
> > or 'connect returned unhandled error' messages if you do.
>
> The pcap trace is not conclusive (enough)?
> I can run with RPCDBG_TRANS enabled, if it is needed to further
> pinpoint the problem.
The pcap trace shows what is happening: the socket is getting closed
correctly, and so the RPC client needs to initiate a reconnection before
it can transmit again. What I don't understand is why it is failing to
do so...
Trond
next prev parent reply other threads:[~2009-11-26 15:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-25 7:35 Fw: Deadlock regression in v2.6.31.6 Andrew Morton
2009-11-25 8:56 ` Stephen R. van den Berg
[not found] ` <64b4daae0911250056g3364d24l98850a272dcfe483-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-11-25 9:00 ` Stephen R. van den Berg
2009-11-25 14:31 ` Trond Myklebust
2009-11-25 21:58 ` Stephen R. van den Berg
2009-11-25 23:11 ` Stephen R. van den Berg
[not found] ` <64b4daae0911251511q7a070b0aj1c07cdc5d6719b41-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-11-26 15:01 ` Trond Myklebust
2009-11-26 15:07 ` Stephen R. van den Berg
[not found] ` <64b4daae0911260707i4064f608w4f7169441640567-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-11-26 15:20 ` Trond Myklebust [this message]
2009-11-27 0:07 ` Stephen R. van den Berg
[not found] ` <64b4daae0911261607m10d1ba3al8c067f85249c198f-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-11-27 0:14 ` Stephen R. van den Berg
[not found] ` <64b4daae0911261614l471fb74fx79db2988f0c65738-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-11-27 21:23 ` Trond Myklebust
2009-11-28 0:20 ` Stephen R. van den Berg
[not found] ` <64b4daae0911271620k46a99666td81528fc863e69f0-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-11-28 15:30 ` Trond Myklebust
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=1259248859.6715.50.camel@localhost \
--to=trond.myklebust@fys.uio.no \
--cc=akpm@linux-foundation.org \
--cc=linux-nfs@vger.kernel.org \
--cc=srb-PCMv+cxZuL0@public.gmane.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