public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Stephen R. van den Berg" <srb-PCMv+cxZuL0@public.gmane.org>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-nfs@vger.kernel.org
Subject: Re: Fw: Deadlock regression in v2.6.31.6
Date: Sat, 28 Nov 2009 01:20:07 +0100	[thread overview]
Message-ID: <64b4daae0911271620k46a99666td81528fc863e69f0@mail.gmail.com> (raw)
In-Reply-To: <1259357036.3486.38.camel@localhost>

On Fri, Nov 27, 2009 at 22:23, Trond Myklebust
<trond.myklebust@fys.uio.no> wrote:
> On Fri, 2009-11-27 at 01:14 +0100, Stephen R. van den Berg wrote:
>> On Fri, Nov 27, 2009 at 01:07, Stephen R. van den Berg <srb-PCMv+cxZuL0@public.gmane.org>=
 wrote:
> Does the following patch fix matters?

> =A0 =A0 =A0 =A0if (!xprt_lock_write(xprt, task))
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0return;
> +
> + =A0 =A0 =A0 if (test_and_clear_bit(XPRT_CLOSE_WAIT, &xprt->state))
> + =A0 =A0 =A0 =A0 =A0 =A0 =A0 xprt->ops->close(xprt);
> +
> =A0 =A0 =A0 =A0if (xprt_connected(xprt))

Sorry.  No go.  I got the following trace, I'm not sure if this is
relevant, because it is difficult to determine if the logging
corresponds to the experienced problem.

RPC: 14194 xprt_connect_status: retrying
RPC: 14194 xprt_prepare_transmit
RPC: 14194 xprt_transmit(112)
RPC:       disconnected transport cfa82400
RPC: 14194 xprt_connect xprt cfa82400 is not connected
RPC: 14194 xprt_connect_status: retrying
RPC: 14194 xprt_prepare_transmit
RPC: 14194 xprt_transmit(112)
RPC:       disconnected transport cfa82400
RPC: 14194 xprt_connect xprt cfa82400 is not connected
RPC: 14194 xprt_connect_status: retrying
RPC: 14194 xprt_prepare_transmit
RPC: 14194 xprt_transmit(112)
RPC:       disconnected transport cfa82400
RPC: 14194 xprt_connect xprt cfa82400 is not connected
RPC: 14194 xprt_connect_status: retrying
RPC: 14194 xprt_prepare_transmit
RPC: 14194 xprt_transmit(112)
RPC:       disconnected transport cfa82400
RPC: 14194 xprt_connect xprt cfa82400 is not connected
RPC: 14194 xprt_connect_status: retrying
RPC: 14194 xprt_prepare_transmit
RPC: 14194 xprt_transmit(112)
--=20
Sincerely,
                Stephen R. van den Berg.

  reply	other threads:[~2009-11-28  0: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
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 [this message]
     [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=64b4daae0911271620k46a99666td81528fc863e69f0@mail.gmail.com \
    --to=srb-pcmv+cxzul0@public.gmane.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trond.myklebust@fys.uio.no \
    /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