> > In messaFrom owner-linux-kernel-outgoing@vger.rutgers.edu Sun Jun 30 13:50:12 1996
Received: from orchard.washtenaw.cc.mi.us (orchard.washtenaw.cc.mi.us [198.111.176.4]) by herbie.ucs.indiana.edu (8.6.12/8.6.12) with ESMTP id NAA06736 for <linuxkernel@herbie.ucs.indiana.edu>; Sun, 30 Jun 1996 13:50:12 -0500
Received: from vger.rutgers.edu by orchard.washtenaw.cc.mi.us (8.6.10/2.3)
with ESMTP id OAA16562; Sun, 30 Jun 1996 14:51:26 -0400
Received: by vger.rutgers.edu id <105662-11720>; Sun, 30 Jun 1996 14:42:45 -0500
From: "A.N.Kuznetsov" <kuznet@ms2.inr.ac.ru>
Message-Id: <199606301841.WAA05066@ms2.inr.ac.ru>
Subject: Re: Recipe for disaster
To: schenk@cs.toronto.edu (Eric Schenk)
Date: Sun, 30 Jun 1996 22:41:50 +0400 (MSD)
Cc: linux-kernel@vger.rutgers.edu
In-Reply-To: <96Jun30.140332edt.15372@dvp.cs.toronto.edu> from "Eric Schenk" at Jun 30, 96 02:03:28 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Length: 510
Sender: owner-linux-kernel@vger.rutgers.edu
Precedence: bulk
Hello!
> While I'm writing, I just noticed a posting on comp.os.linux.networking
> that complains that you can freeze a linux kernel by opening up
> a socket pair and dumping a couple of dozen megabytes of data across it
> in one chunk.
Note, that my fix to dev.c will not cure this problem.
I was afraid that extensive dropping could break router/bridge,
when working on interrupt at peak loads is normal and
dropped just ONE packet.
Change break to continue to cure the second problem.
Alexey Kuznetsov.