From: Just Marc <marc@corky.net>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: netdev@axxeo.de, netdev@vger.kernel.org
Subject: Re: Disabling "TCP Treason uncloaked"
Date: Wed, 03 May 2006 14:25:25 +0100 [thread overview]
Message-ID: <4458AF45.9050108@corky.net> (raw)
In-Reply-To: <E1FbGCo-0000OS-00@gondolin.me.apana.org.au>
Hi
> Just Marc <marc@corky.net> wrote:
>
>>
>> That's good, but it may (and probably will) suppress many other messages
>> which may be of more interest...
>>
>
> That's the crux of the matter. There is no way we can satisfy everyone
> short of putting a knob on each individual printk.
>
> So the only solution is to do the filtering yourself in userspace through
> klogd/syslogd.
>
It is the crux of the matter. This print is a purely informational one,
absolutely harmless (unless I'm mistaken) and clogs kernel logs
throughout the universe :)
Seriously, other kernel prints are usually not so harmless and are
generally more important to see. Let me put it another way, except
this print, I have no other prints whatsoever on any of my machines and
if there are prints, I usually do want to know about them, I learned to
ignore this print over the years. I believe many people are in the
same boat.
That's my opinion, anyway.
Thanks
next prev parent reply other threads:[~2006-05-03 12:26 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 [this message]
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=4458AF45.9050108@corky.net \
--to=marc@corky.net \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@axxeo.de \
--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.