diff mbox

xprt_wait_for_buffer_space changes causes a hang.

Message ID 1392129211.5763.5.camel@leira.trondhjem.org (mailing list archive)
State New, archived
Headers show

Commit Message

Trond Myklebust Feb. 11, 2014, 2:33 p.m. UTC
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.

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(-)

Comments

NeilBrown Feb. 12, 2014, 4:05 a.m. UTC | #1
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.

By the way, this bug is the first time that I've found the tasklisk - printed
when you enable rpc debuging - useful.  And it was *really* useful!

There were lots of

nfsv3 WRITE a:call_reserveresult q:xprt_backlog

and a few

nfsv3 WRITE a:call_status q:xprt_sending

and one

nfsv3 WRITE a:call_transmit_status q:xprt_pending

That last one was put to sleep by xprt_wait_for_buffer_space() and
is blocking all the rest.


Now I've got another bug with vaguely similar symptoms and only

9bfb000   (null)        0 ffffffffa03aa0a0 nfsv3 READ a:call_reserveresult q:xprt_sending
9bfb000   (null)        0 ffffffffa03aa0a0 nfsv3 READ a:call_reserveresult q:xprt_sending
a933000   (null)        0 ffffffffa03084e0 nfsv3 ACCESS a:call_reserveresult q:xprt_sending

I suspect it is a different bug.  Maybe some missing backports or something,
though we have 961a828df64979d2a which is related code.

Thanks,
NeilBrown
NeilBrown Feb. 17, 2014, 12:18 a.m. UTC | #2
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
diff mbox

Patch

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;
 }