From: Just Marc <marc@corky.net>
To: "David S. Miller" <davem@davemloft.net>
Cc: ak@suse.de, netdev@vger.kernel.org
Subject: Re: Disabling "TCP Treason uncloaked"
Date: Wed, 03 May 2006 09:06:30 +0100 [thread overview]
Message-ID: <44586486.70702@corky.net> (raw)
In-Reply-To: <20060502.233246.92272407.davem@davemloft.net>
> From: Andi Kleen <ak@suse.de>
> Date: Tue, 2 May 2006 18:02:43 +0200
>
>
>> On Tuesday 02 May 2006 18:19, Just Marc wrote:
>>
>>
>>> I thought that maybe it's time to either set TCP_DEBUG to 0 or
>>> alternatively allow an admin to toggle the printing of this message
>>> off/on? On a few busy web servers running usually latest versions of
>>> 2.6 I have this message displaying hundreds (if not more) times a day,
>>>
>> You're talking to a lot of broken TCP clients then.
>>
>
> Herbert Xu also fixed a bug that would cause that message
> to be emitted erroneously, 9 times out of 10 that is why
> people are seeing these messages.
>
> I think disabling that message is a non-starter, we want to
> see the message because as we've seen it can point to bugs
> on our end too.
>
>
Correct, I noticed this was applied to 2.6.14, however, I am running
2.6.16 (and now 2.6.16.12) on all of the machines in question, I am
seeing hundreds of these messages a day...
Thanks
next prev parent reply other threads:[~2006-05-03 7:07 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 [this message]
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
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=44586486.70702@corky.net \
--to=marc@corky.net \
--cc=ak@suse.de \
--cc=davem@davemloft.net \
--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).