All of lore.kernel.org
 help / color / mirror / Atom feed
From: Just Marc <marc@corky.net>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: netdev@vger.kernel.org
Subject: Re: Disabling "TCP Treason uncloaked"
Date: Wed, 03 May 2006 13:49:05 +0100	[thread overview]
Message-ID: <4458A6C1.90103@corky.net> (raw)
In-Reply-To: <E1FbBPy-0007Iu-00@gondolin.me.apana.org.au>

Hi,
> Just Marc <marc@corky.net> wrote:
>   
>> We're now at 2.6.16.12 and it is still showing thousands of times a day 
>> on a busy web server, have all the bugs been discovered yet?
>>     
>
> There are no known bugs on the RX side in 2.6.16 that would cause this.
> The few busy web servers that I have access to do not see this message
> at all.
>
> So either your web server is somehow attracting a lot of buggy TCP stacks,
> or there could be a dodgy gateway in your path that is mucking with the
> TCP windows.
>
>   
You're right, actually this box serves http/ftp file transfers only, 
it's a mirror with a large amount of downloads a day.

On a pure html/image web server that is just as busy, there are only a 
few of these messages, one or two a day.
> I suggest that you do a tcpdump to see what it looks like.  It might turn
> out that we do still have a bug on our RX side.
>   
I gave it another look, many of the prints are repeat prints for the 
same remote IPs,
> BTW, this message is already under net_ratelimit so I don't see any
> urgency in getting rid of it completely.  If we're going down the
> path of disabling it, we probably should go for something more global
> rather than a sysctl that controls this one message.
>   
I agree, however, I think it's pretty good to allow an admin to toggle 
it off completely.  Maybe that's all we need, really.

Thanks

  parent reply	other threads:[~2006-05-03 11:50 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-02 16:19 Disabling "TCP Treason uncloaked" Just Marc
2006-05-02 16:02 ` Andi Kleen
2006-05-03  4:44   ` Just Marc
2006-05-03  6:32   ` David S. Miller
2006-05-03  6:52     ` Andi Kleen
2006-05-03  8:06     ` Just Marc
2006-05-02 23:00 ` Herbert Xu
2006-05-03  4:10   ` Auke Kok
2006-05-03  4:46   ` Just Marc
2006-05-03  7:05     ` Herbert Xu
2006-05-03 11:47       ` Ingo Oeser
2006-05-03 12:21         ` Herbert Xu
2006-05-03 13:08         ` Just Marc
2006-05-03 12:11           ` Herbert Xu
2006-05-03 13:25             ` Just Marc
2006-05-03 12:49       ` Just Marc [this message]
2006-05-03 11:56         ` Herbert Xu
2006-05-03 12:15           ` Alexey Toptygin
2006-05-03 13:19             ` Herbert Xu
2006-05-03 13:11           ` Just Marc

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=4458A6C1.90103@corky.net \
    --to=marc@corky.net \
    --cc=herbert@gondor.apana.org.au \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.