From owner-cvs-src@FreeBSD.ORG Sat Oct 9 14:14:47 2004 Return-Path: Delivered-To: cvs-src@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8D2DE16A4CE; Sat, 9 Oct 2004 14:14:47 +0000 (GMT) Received: from smtp.des.no (flood.des.no [217.116.83.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E87443D4C; Sat, 9 Oct 2004 14:14:47 +0000 (GMT) (envelope-from des@des.no) Received: by smtp.des.no (Pony Express, from userid 666) id 6FFCC530A; Sat, 9 Oct 2004 16:14:46 +0200 (CEST) Received: from dwp.des.no (des.no [80.203.228.37]) by smtp.des.no (Pony Express) with ESMTP id 9862D5311; Sat, 9 Oct 2004 16:14:39 +0200 (CEST) Received: by dwp.des.no (Postfix, from userid 2602) id 737B2B85E; Sat, 9 Oct 2004 16:14:39 +0200 (CEST) To: Brian Feldman References: <200410082019.i98KJTTd026310@repoman.freebsd.org> From: des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=) Date: Sat, 09 Oct 2004 16:14:39 +0200 In-Reply-To: <200410082019.i98KJTTd026310@repoman.freebsd.org> (Brian Feldman's message of "Fri, 8 Oct 2004 20:19:29 +0000 (UTC)") Message-ID: User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on flood.des.no X-Spam-Level: X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.64 cc: cvs-src@FreeBSD.org cc: src-committers@FreeBSD.org cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/vm uma_core.c uma_dbg.c X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Oct 2004 14:14:49 -0000 Brian Feldman writes: > Log: > Fix critical stability problems that can cause UMA mbuf cluster > state management corruption, mbuf leaks, general mbuf corruption, > and at least on i386 a first level splash damage radius that > encompasses up to about half a megabyte of the memory after > an mbuf cluster's allocation slab. In short, this has caused > instability nightmares anywhere the right kind of network traffic > is present. Do you think you can get this into RELENG_5 before the release (provided re@ agrees)? DES --=20 Dag-Erling Sm=F8rgrav - des@des.no