netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: damian@tvk.rwth-aachen.de
Cc: denys@visp.net.lb, ilpo.jarvinen@helsinki.fi, netdev@vger.kernel.org
Subject: Re: [PATCH] tcp: fix ICMP-RTO war
Date: Mon, 25 Jan 2010 23:45:57 -0800 (PST)	[thread overview]
Message-ID: <20100125.234557.00486980.davem@davemloft.net> (raw)
In-Reply-To: <4B5DB3BF.1080409@tvk.rwth-aachen.de>

From: Damian Lukowski <damian@tvk.rwth-aachen.de>
Date: Mon, 25 Jan 2010 16:07:43 +0100

> @@ -530,7 +530,11 @@ static inline void tcp_bound_rto(const struct sock *sk)
>  
>  static inline u32 __tcp_set_rto(const struct tcp_sock *tp)
>  {
> -	return (tp->srtt >> 3) + tp->rttvar;
> +	u32 rto = (tp->srtt >> 3) + tp->rttvar;
> +	if (unlikely(rto < TCP_RTO_MIN))
> +		return TCP_RTO_MIN;
> +	else
> +		return rto;
>  }

The min RTO is now a runtime variable, TCP_RTO_MIN is merely the
default, so we should use tcp_rto_min() for obtaining that value.

And if we make this change, we might want to delete the comment in
tcp_set_rto() which claims:

	/* NOTE: clamping at TCP_RTO_MIN is not required, current algo
	 * guarantees that rto is higher.
	 */
	tcp_bound_rto(sk);

And we have shown here at least one case where that is not true.
:-)

I've looked at Denys's traces and your analysis, and I still
can't figure out who the true culprit is that lets us get into
such a state that RTO is evaluated so low...

  reply	other threads:[~2010-01-26  7:45 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-26 15:03 Crazy TCP bug (keepalive flood?) in 2.6.32? Denys Fedoryshchenko
2009-12-26 19:24 ` Ilpo Järvinen
2010-01-11 13:02 ` Ilpo Järvinen
2010-01-16 14:12   ` Denys Fedoryshchenko
2010-01-19  9:10     ` Damian Lukowski
2010-01-19 11:09       ` Denys Fedoryshchenko
2010-01-19 11:17         ` Ilpo Järvinen
2010-01-23 21:37           ` Denys Fedoryshchenko
2010-01-23 22:34             ` [PATCH] tcp: fix ICMP-RTO war Ilpo Järvinen
2010-01-23 22:45               ` Denys Fedoryshchenko
2010-01-25 15:07                 ` Damian Lukowski
2010-01-26  7:45                   ` David Miller [this message]
2010-01-27 12:41                     ` Ilpo Järvinen
2010-01-27 14:14                       ` Alexey Kuznetsov
2010-01-23 23:28               ` Denys Fedoryshchenko
2010-01-25 12:12               ` Damian Lukowski
2010-01-27 12:36                 ` Ilpo Järvinen
  -- strict thread matches above, loose matches on Subject: below --
2010-01-27 13:56 Denys Fedoryshchenko
2010-01-29 12:13 ` Damian Lukowski
2010-01-29 15:15   ` Denys Fedoryshchenko
2010-01-29 21:45     ` Damian Lukowski
2010-01-30 13:35       ` Denys Fedoryshchenko
2010-01-30 13:56         ` Damian Lukowski
2010-02-07 10:28           ` Denys Fedoryshchenko

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=20100125.234557.00486980.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=damian@tvk.rwth-aachen.de \
    --cc=denys@visp.net.lb \
    --cc=ilpo.jarvinen@helsinki.fi \
    --cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).