netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@vyatta.com>
To: "Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi>
Cc: David Miller <davem@davemloft.net>, Netdev <netdev@vger.kernel.org>
Subject: Re: TCP: Peer messages
Date: Sun, 19 Apr 2009 20:11:00 -0700	[thread overview]
Message-ID: <20090419201100.55bfb6bb@nehalam> (raw)
In-Reply-To: <Pine.LNX.4.64.0904191408090.21005@wrl-59.cs.helsinki.fi>

On Sun, 19 Apr 2009 14:19:36 +0300 (EEST)
"Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi> wrote:

> On Sat, 18 Apr 2009, Stephen Hemminger wrote:
> 
> > Running some log-term tests of (using bittorrent of latest Ubuntu releases).
> > I see no problems with firewall rules (or sky2 driver), but I do several 
> > of these: 
> > 
> > 
> > [28286.893945] TCP: Peer <ip scrubbed>:63659/51413 unexpectedly shrunk window 414881290:414894358 (repaired)
> > [47312.851937] TCP: Peer <ip scrubbed>:43793/51413 unexpectedly shrunk window 888816585:888823785 (repaired)
> 
> This is what was earlier the Treason uncloacked message until somebody 
> was scared to death because of it and we had to change the wording.
> 
> And it's what the old kernels do for us (and there are plenty of such 
> kernels around), and possibly broken middleboxes too. Unless you have a 
> tcpdump of a specific case or can clearly say that its frequency is much 
> larger than it used to be in some between kernel versions consistent test 
> setup, I'm not going to waste my time on debugging obsolete remote ends.
> 
> But, now that I think it a bit more, we could possibly but a WARN_ON 
> somewhere if we ever sent past advertized window to make a distinction 
> between our and their bugs.
> 

12 over 3 days is not enough to worry about.

      reply	other threads:[~2009-04-20  3:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-19  1:03 TCP: Peer messages Stephen Hemminger
2009-04-19 11:19 ` Ilpo Järvinen
2009-04-20  3:11   ` Stephen Hemminger [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=20090419201100.55bfb6bb@nehalam \
    --to=shemminger@vyatta.com \
    --cc=davem@davemloft.net \
    --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).