public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Trond Myklebust <trond.myklebust@primarydata.com>
Cc: NFS <linux-nfs@vger.kernel.org>
Subject: Re: xprt_wait_for_buffer_space changes causes a hang.
Date: Mon, 17 Feb 2014 11:18:47 +1100	[thread overview]
Message-ID: <20140217111847.61919989@notabene.brown> (raw)
In-Reply-To: <20140212150555.60d6d9a7@notabene.brown>

[-- Attachment #1: Type: text/plain, Size: 4130 bytes --]

On Wed, 12 Feb 2014 15:05:55 +1100 NeilBrown <neilb@suse.de> wrote:

> On Tue, 11 Feb 2014 09:33:31 -0500 Trond Myklebust
> <trond.myklebust@primarydata.com> wrote:
> 
> > On Mon, 2014-02-10 at 17:03 +1100, NeilBrown wrote:
> > > Hi,
> > >  We have a customer who reports occasional but reproducible hangs on our 3.0
> > >  based kernel.
> > >  I managed to deduce that 
> > > 
> > > commit a9a6b52ee1baa865283a91eb8d443ee91adfca56
> > > Author: Trond Myklebust <Trond.Myklebust@netapp.com>
> > > Date:   Fri Feb 22 14:57:57 2013 -0500
> > > 
> > >     SUNRPC: Don't start the retransmission timer when out of socket space
> > >  
> > > was to blame (it got into our kernel through -stable ... not sure why it
> > > deserved to be in -stable). Reverting that patch fixes the problem.  However I
> > > don't fully understand why.
> > > 
> > 
> > The reason why that patch was put into stable was that the connection
> > breakage triggered by the timeouts was causing nasty behaviour when
> > servers (or the network) are heavily loaded. Instead of clearing the
> > logjam, breaking the connection and then reconnecting would aggravate
> > it, causing hangs.
> 
> Ahh, that make sense.  Thanks.
> 
> 
> > 
> > Anyhow, does the following patch help to break the race?
> > 8<------------------------------------------------------------------
> > >From e4c0373be4b8deae2667a7478d34415b99924abc Mon Sep 17 00:00:00 2001
> > From: Trond Myklebust <trond.myklebust@primarydata.com>
> > Date: Tue, 11 Feb 2014 09:15:54 -0500
> > Subject: [PATCH] SUNRPC: Fix races in xs_nospace()
> > 
> > When a send failure occurs due to the socket being out of buffer space,
> > we call xs_nospace() in order to have the RPC task wait until the
> > socket has drained enough to make it worth while trying again.
> > The current patch fixes a race in which the socket is drained before
> > we get round to setting up the machinery in xs_nospace(), and which
> > is reported to cause hangs.
> > 
> > Link: http://lkml.kernel.org/r/20140210170315.33dfc621@notabene.brown
> > Fixes: a9a6b52ee1ba (SUNRPC: Don't start the retransmission timer...)
> > Reported-by: Neil Brown <neilb@suse.com>
> > Cc: stable@vger.kernel.org
> > Signed-off-by: Trond Myklebust <trond.myklebust@primarydata.com>
> > ---
> >  net/sunrpc/xprtsock.c | 6 +++++-
> >  1 file changed, 5 insertions(+), 1 deletion(-)
> > 
> > diff --git a/net/sunrpc/xprtsock.c b/net/sunrpc/xprtsock.c
> > index 6497c221612c..966763d735e9 100644
> > --- a/net/sunrpc/xprtsock.c
> > +++ b/net/sunrpc/xprtsock.c
> > @@ -510,6 +510,7 @@ static int xs_nospace(struct rpc_task *task)
> >  	struct rpc_rqst *req = task->tk_rqstp;
> >  	struct rpc_xprt *xprt = req->rq_xprt;
> >  	struct sock_xprt *transport = container_of(xprt, struct sock_xprt, xprt);
> > +	struct sock *sk = transport->inet;
> >  	int ret = -EAGAIN;
> >  
> >  	dprintk("RPC: %5u xmit incomplete (%u left of %u)\n",
> > @@ -527,7 +528,7 @@ static int xs_nospace(struct rpc_task *task)
> >  			 * window size
> >  			 */
> >  			set_bit(SOCK_NOSPACE, &transport->sock->flags);
> > -			transport->inet->sk_write_pending++;
> > +			sk->sk_write_pending++;
> >  			/* ...and wait for more buffer space */
> >  			xprt_wait_for_buffer_space(task, xs_nospace_callback);
> >  		}
> > @@ -537,6 +538,9 @@ static int xs_nospace(struct rpc_task *task)
> >  	}
> >  
> >  	spin_unlock_bh(&xprt->transport_lock);
> > +
> > +	/* Race breaker in case memory is freed before above code is called */
> > +	sk->sk_write_space(sk);
> >  	return ret;
> >  }
> >  
> 
> I looks good.  I've asked if the customer is willing to test it and provided
> the patch.

Unfortunately the customer was not able to get internal approval to test this
patch, as they already have a working solution.

So we might have to go with this patch without confirmation that it fixes
this particular problem.  I've examined it again and I cannot see any room
for any new races, and it should fix a credible problem.
So
  Reviewed-by: NeilBrown <neilb@suse.de>

Thanks,
NeilBrown

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

      reply	other threads:[~2014-02-17  0:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-10  6:03 xprt_wait_for_buffer_space changes causes a hang NeilBrown
2014-02-11 14:33 ` Trond Myklebust
2014-02-12  4:05   ` NeilBrown
2014-02-17  0:18     ` NeilBrown [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=20140217111847.61919989@notabene.brown \
    --to=neilb@suse.de \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trond.myklebust@primarydata.com \
    /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