[3515] in linux-net channel archive
Re: The crash 2.0 tcp program
daemon@ATHENA.MIT.EDU (Alan Cox)
Thu Jun 27 04:50:32 1996
From: Alan Cox <alan@cymru.net>
To: schenk@cs.toronto.edu (Eric Schenk)
Date: Thu, 27 Jun 1996 09:23:29 +0100 (BST)
Cc: alan@lxorguk.ukuu.org.uk, linux-net@vger.rutgers.edu,
schenk@cs.toronto.edu, torvalds@cs.helsinki.fi
In-Reply-To: <96Jun26.201617edt.15381@dvp.cs.toronto.edu> from "Eric Schenk" at Jun 26, 96 08:16:16 pm
> This might explain a couple of tcpdump's I've received that I
> just couldn't understand. The obvious fix is to seperate the
> setting of real delayed acks from the setting of a delayed
> ack because we have no memory. Say introduce tcp_resend_ack()
> which would take care of scheduling an ack if we can't get
> enough memory. The alternative is to just drop the ack if
> we haven't got enough memory, but I don't much like that alternative.
> Anyone see a problem with this approach?
No I tested that last night. It stops that problem, but its not the cause of
the crash program, thats something else presumably similar as it still takes
out the machine in some kind of loopback food fight between two tcp sockets.
Alan
