From owner-freebsd-arch Tue Nov 7 22:29:35 2000 Delivered-To: freebsd-arch@freebsd.org Received: from critter.freebsd.dk (fw2.aub.dk [195.24.1.195]) by hub.freebsd.org (Postfix) with ESMTP id 36A6137B479 for ; Tue, 7 Nov 2000 22:29:31 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.9.3) with ESMTP id eA86T6D29405; Wed, 8 Nov 2000 07:29:06 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Andre Oppermann Cc: Paul Saab , arch@FreeBSD.ORG Subject: Re: Green/Yellow/Red state for the VM system. In-Reply-To: Your message of "Wed, 08 Nov 2000 00:39:39 +0100." <3A0892BB.4F399708@telehouse.ch> Date: Wed, 08 Nov 2000 07:29:06 +0100 Message-ID: <29403.973664946@critter> From: Poul-Henning Kamp Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3A0892BB.4F399708@telehouse.ch>, Andre Oppermann writes: >> > I don't think this is necessary at all after Matt's and Paul's code >> > being commited. Why? Because the box would not wedge solid or panic >> > anymore. >> >> I wouldn't make such a bold statement.. We find all sorts of interesting >> bugs on a daily basis and I would bet money we'll find another way to >> lockup the system. > >OK, but would the right solution be to simply make more memory >available? I doubt it. A bug is a bug and needs to be fixed not >to be masked. Eventually it would fail just in a different place. You overlook the fact that my change will be an automatic remedy for several classes of DoS. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message