Hello!
> > If my guess is right, you can easily put this socket to funny state
> > just catting a large file and kill -STOP'ing ssh. ssh will close window,
> > but sshd will not send zero probes.
>
> [1] I have checked your statement on 2 different machines, running 2.2.17.
> No confirmation. But this is much more funny than it simply sounds. :)
_That_ socket which was stuck must show this behaviour.
To get this on new socket you should leave session idle for >2hours
until the first keeplaive. After this it will never probe under
any curcumstances. The bug was that keepalive corrupts state of timer
and probe0 timer is not started after this.
> buffer is filled, and client IS NOT stopped! :))) Hence connection dies
> due to retransmission timeout on the server side.
It is known linuxism. If the ratio connection_mss/link_mtu less than ~1/4
or connection is flood with tiny packets, after rcvbuf is full linux
enters memory paranoia mode pretending that all the packets are lost.
Ugly, unpleasant, but luckily harmless under any normal curcumstances.
One way to workaround is to set rx_copybreak on ethernet drivers to 400-500.
The bug is really difficult. It is not cured even in current 2.4
(only with zerocopy patch).
> I do not understand how connection with closed window can wait until
> first keepalive - it must do zero probes instead.
If socket has ever sent keepalive, it will not be able to send zero window
probes after this.
> Hmm... I observed this bug on the host, which never performs more
> than 10 conn/sec and has peak loadvg ~ 0.15.
8)8)8) Probability is probability.
Alexey
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Apr 15 2001 - 21:00:16 EST