From: Simon Kirby <sim@hostway.ca>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: David Miller <davem@davemloft.net>,
tglx@linutronix.de, netdev@vger.kernel.org,
a.p.zijlstra@chello.nl, linux-kernel@vger.kernel.org,
davej@redhat.com, schwidefsky@de.ibm.com, mingo@elte.hu
Subject: Re: [3.1] Divide by zero in __tcp_select_window()
Date: Wed, 16 Nov 2011 11:54:19 -0800 [thread overview]
Message-ID: <20111116195419.GE24411@hostway.ca> (raw)
In-Reply-To: <1321304216.2719.23.camel@edumazet-laptop>
On Mon, Nov 14, 2011 at 09:56:56PM +0100, Eric Dumazet wrote:
> Le lundi 14 novembre 2011 ?? 15:36 -0500, David Miller a ??crit :
> > From: Eric Dumazet <eric.dumazet@gmail.com>
> > Date: Tue, 08 Nov 2011 22:23:25 +0100
> >
> > > OK, it seems we let a timer running while we free the socket (same error
> > > path than your previous bug report, because of the NULL route)
> > >
> > > We arm this keepalive timer in tcp_create_openreq_child()
> > >
> > > net/ipv4/tcp_minisocks.c:513
> > > if (sock_flag(newsk, SOCK_KEEPOPEN))
> > > inet_csk_reset_keepalive_timer(newsk,
> > > keepalive_time_when(newtp));
> > >
> > > I would try to add a call to tcp_clear_xmit_timers() as well
> > >
> > > Please try following patch :
> >
> > We've been waiting quite some time to get some testing validation on
> > this patch, but I think it's correct.
> >
> > Eric can you formally submit this? Thanks!
>
> Sure, here it is.
>
> Please Simon feel free to add your "Tested-by" signature
>
> Thanks
Looks good, thanks! Working on ~25 boxes without issue for >36 hours.
Simon-
Tested-by: Simon Kirby <sim@hostway.ca>
> [PATCH] tcp: clear xmit timers in tcp_v4_syn_recv_sock()
>
> Simon Kirby reported divides by zero errors in __tcp_select_window()
>
> This happens when inet_csk_route_child_sock() returns a NULL pointer :
>
> We free new socket while we eventually armed keepalive timer in
> tcp_create_openreq_child()
>
> Fix this by a call to tcp_clear_xmit_timers()
>
> [ This is a followup to commit 918eb39962dff (net: add missing
> bh_unlock_sock() calls) ]
>
> Reported-by: Simon Kirby <sim@hostway.ca>
> Signed-off-by: Eric Dumazet <eric.dumazet@gmail.com>
> ---
> net/ipv4/tcp_ipv4.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/net/ipv4/tcp_ipv4.c b/net/ipv4/tcp_ipv4.c
> index a744315..a9db4b1 100644
> --- a/net/ipv4/tcp_ipv4.c
> +++ b/net/ipv4/tcp_ipv4.c
> @@ -1510,6 +1510,7 @@ exit:
> NET_INC_STATS_BH(sock_net(sk), LINUX_MIB_LISTENDROPS);
> return NULL;
> put_and_exit:
> + tcp_clear_xmit_timers(newsk);
> bh_unlock_sock(newsk);
> sock_put(newsk);
> goto exit;
>
>
next prev parent reply other threads:[~2011-11-16 19:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-08 20:54 [3.1] Divide by zero in __tcp_select_window() Simon Kirby
2011-11-08 21:23 ` Eric Dumazet
2011-11-14 20:36 ` David Miller
2011-11-14 20:44 ` Simon Kirby
2011-11-14 20:56 ` Eric Dumazet
2011-11-16 19:54 ` Simon Kirby [this message]
2011-11-16 20:26 ` Eric Dumazet
2011-11-16 21:58 ` David Miller
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=20111116195419.GE24411@hostway.ca \
--to=sim@hostway.ca \
--cc=a.p.zijlstra@chello.nl \
--cc=davej@redhat.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=netdev@vger.kernel.org \
--cc=schwidefsky@de.ibm.com \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).