From owner-freebsd-current@FreeBSD.ORG  Tue Apr 15 14:11:51 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 631A737B401
	for <FreeBSD-current@freebsd.org>;
	Tue, 15 Apr 2003 14:11:51 -0700 (PDT)
Received: from critter.freebsd.dk (port757.uc1-esp.isdn-lan.cybercity.dk
	[212.242.98.245])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 8E09743FA3
	for <FreeBSD-current@freebsd.org>;
	Tue, 15 Apr 2003 14:11:49 -0700 (PDT)
	(envelope-from phk@phk.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.12.9/8.12.9) with ESMTP id h3FLBk6W030056;
	Tue, 15 Apr 2003 23:11:47 +0200 (CEST)
	(envelope-from phk@phk.freebsd.dk)
To: "Ian Freislich" <ianf@za.uu.net>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Tue, 15 Apr 2003 22:40:20 +0200."
             <55218.1050439220@wcom.com> 
Date: Tue, 15 Apr 2003 23:11:46 +0200
Message-ID: <30054.1050441106@critter.freebsd.dk>
cc: FreeBSD-current@freebsd.org
Subject: Re: Kernel memory leak? 
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2003 21:11:51 -0000

In message <55218.1050439220@wcom.com>, "Ian Freislich" writes:

>Running this program, resulted in my server panicing after about
>15 minutes (15000 iterations).  Watching top, the 'wired' memory
>slowly increases increases until the system panics with the message
>below.  It's very repeatable, so I can get a more detailed backtrace
>if required.

That looks like a memory leak in my department, I'll fix it before 5.1.

Poul-Henning

># There must be a better way to do this

I suggest instead you search for valid superblocks, they have a 
well-defined magic word you could look for.

I even belive I have seen reports of a tool that does it automatically,
but have no references at hand.

-- 
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.