From: Matt Mackall <mpm@selenic.com>
To: "Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi>
Cc: David Miller <davem@davemloft.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH] Stop scaring users with "treason uncloaked!"
Date: Thu, 18 Dec 2008 17:50:34 -0600 [thread overview]
Message-ID: <1229644234.3726.577.camel@calx> (raw)
In-Reply-To: <Pine.LNX.4.64.0812190028560.12061@wrl-59.cs.helsinki.fi>
On Fri, 2008-12-19 at 00:33 +0200, Ilpo Järvinen wrote:
> On Thu, 18 Dec 2008, Matt Mackall wrote:
>
> > These debug messages are uninformative and extremely alarming. Rather
> > than reporting a peer as a treacherous attacker, report it more
> > correctly as simply broken.
>
> Last time (well, ignoring some report on ancient vendor kernel) I've seen
> this to trigger it wasn't the fault of the peer but ours (we sent past the
> advertized window and window ended up being shrunk to zero). I agree that
> the message as-is is not very good but your change is not very good
> either.
Here this is the bulk of messages on my server (which is otherwise
fairly quiet).
It really doesn't matter whether the message is technically accurate -
it's mostly there for the benefit of kernel hackers. The average end
user is not going to have the slightest clue what is going on nor should
they even care. An advanced network admin might be able to figure things
out by poking at packet traces, but again: not much reason to care. For
most admins, the vast majority of these treasonous peers won't be under
their administrative control.
If you want, we can instead say "Peer %d unexpectedly shrunk window...".
So long as the scary bit is gone, I don't care.
--
Mathematics is the supreme nostalgia of our time.
next prev parent reply other threads:[~2008-12-18 23:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-18 22:16 [PATCH] Stop scaring users with "treason uncloaked!" Matt Mackall
2008-12-18 22:33 ` Ilpo Järvinen
2008-12-18 22:36 ` Herbert Xu
2008-12-18 23:50 ` Matt Mackall [this message]
2008-12-19 0:15 ` David Miller
2008-12-19 3:49 ` Matt Mackall
2008-12-19 3:54 ` David Miller
2008-12-19 18:13 ` markus reichelt
2008-12-19 0:08 ` David Miller
2008-12-18 22:44 ` Herbert Xu
2008-12-18 22:49 ` Alan Cox
2008-12-18 23:02 ` Herbert Xu
2008-12-18 23:14 ` Alan Cox
2008-12-19 0:07 ` David Miller
2008-12-18 23:06 ` Matt Mackall
2008-12-19 0:45 ` David Schwartz
2008-12-19 0:55 ` Krzysztof Halasa
2008-12-19 0:58 ` Rick Jones
2009-01-26 17:46 ` Lennart Sorensen
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=1229644234.3726.577.camel@calx \
--to=mpm@selenic.com \
--cc=davem@davemloft.net \
--cc=ilpo.jarvinen@helsinki.fi \
--cc=linux-kernel@vger.kernel.org \
--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