From owner-freebsd-current@FreeBSD.ORG Tue Jun 22 09:49:48 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 38F9F16A4CE; Tue, 22 Jun 2004 09:49:48 +0000 (GMT) Received: from smtp.des.no (flood.des.no [217.116.83.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 005C643D1F; Tue, 22 Jun 2004 09:49:48 +0000 (GMT) (envelope-from des@des.no) Received: by smtp.des.no (Pony Express, from userid 666) id 3DFAA530D; Tue, 22 Jun 2004 11:49:25 +0200 (CEST) Received: from dwp.des.no (des.no [80.203.228.37]) by smtp.des.no (Pony Express) with ESMTP id 997F35309; Tue, 22 Jun 2004 11:49:18 +0200 (CEST) Received: by dwp.des.no (Postfix, from userid 2602) id 4E7A7B86C; Tue, 22 Jun 2004 11:49:18 +0200 (CEST) To: Maxim Konovalov References: <40D754D5.1070805@freebsd.org> <20040622115532.W5744@mp2.macomnet.net> <20040622132451.K6489@mp2.macomnet.net> From: des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=) Date: Tue, 22 Jun 2004 11:49:18 +0200 In-Reply-To: <20040622132451.K6489@mp2.macomnet.net> (Maxim Konovalov's message of "Tue, 22 Jun 2004 13:29:52 +0400 (MSD)") 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.63 (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.63 cc: freebsd-net@freebsd.org cc: freebsd-current@freebsd.org cc: Andre Oppermann Subject: Re: New preview patch for ipfw to pfil_hooks conversion X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jun 2004 09:49:48 -0000 Maxim Konovalov writes: > Yesterday -CURRENT leaks kernel memory very quickly and panics after > 10 - 15 mins up. Nope. That bug was introduced on June 9th, almost two weeks ago, and it was fixed less than twelve hours later. I have several machines already running yesterday's -CURRENT, and none of them show signs of any kind of leak. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no