From: Andres Salomon <dilinger@mp3revolution.net>
To: "Marco d'Itri" <md@Linux.IT>
Cc: linux-kernel@vger.kernel.org
Subject: Re: peer shrinks window
Date: Fri, 9 Mar 2001 22:25:29 -0500 [thread overview]
Message-ID: <20010309222529.A28615@mp3revolution.net> (raw)
In-Reply-To: <20010310004556.A7380@wonderland.linux.it>
In-Reply-To: <20010310004556.A7380@wonderland.linux.it>; from md@Linux.IT on Sat, Mar 10, 2001 at 12:45:56AM +0100
I've noticed this as well in my logs. In linux/include/net/tcp.h,
TCP_DEBUG is turned on; in linux/net/ipv4/tcp_input.c,
tcp_ack_update_window() contains the following:
#ifdef TCP_DEBUG
<snip>
printk(KERN_DEBUG "TCP: peer %u.%u.%u.%u:%u/%u shrinks window %u:%u:%u. Bad, what else can I say?\n",
NIPQUAD(sk->daddr), htons(sk->dport), sk->num,
tp->snd_una, tp->snd_wnd, tp->snd_nxt);
<snip>
#endif
Is it really necessary for TCP_DEBUG to be turned on by default?
On Sat, Mar 10, 2001 at 12:45:56AM +0100, Marco d'Itri wrote:
>
> In two days I've got 46 messages like:
>
> Mar 7 08:00:55 attila kernel: TCP: peer 163.162.41.4:37582/20 shrinks window 752789960:5840:752797200. Bad, what else can I say?
>
> If needed I can ask about the os running there, I think it's solaris.
> (nmap confirms: Solaris 7)
>
> Linux attila 2.4.0-test11 #11 Wed Dec 13 12:02:51 CET 2000 ppc unknown
>
> --
> ciao,
> Marco
--
"... being a Linux user is sort of like living in a house inhabited
by a large family of carpenters and architects. Every morning when
you wake up, the house is a little different. Maybe there is a new
turret, or some walls have moved. Or perhaps someone has temporarily
removed the floor under your bed." - Unix for Dummies, 2nd Edition
-- found in the .sig of Rob Riggs, rriggs@tesser.com
prev parent reply other threads:[~2001-03-10 3:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-09 23:45 Marco d'Itri
2001-03-10 3:25 ` Andres Salomon [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=20010309222529.A28615@mp3revolution.net \
--to=dilinger@mp3revolution.net \
--cc=linux-kernel@vger.kernel.org \
--cc=md@Linux.IT \
/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
all inboxes | Powered by JetHome®