From owner-freebsd-current@FreeBSD.ORG  Sun Jul 27 22:46:52 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 12B4F37B401; Sun, 27 Jul 2003 22:46:52 -0700 (PDT)
Received: from mail.cyberonic.com (mail.cyberonic.com [4.17.179.4])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 1DBE343F85; Sun, 27 Jul 2003 22:46:51 -0700 (PDT)
	(envelope-from jmg@hydrogen.funkthat.com)
Received: from hydrogen.funkthat.com (node-40244c0a.sfo.onnet.us.uu.net
	[64.36.76.10])
	by mail.cyberonic.com (8.12.8/8.12.5) with ESMTP id h6S6IN0n032530;
	Mon, 28 Jul 2003 02:18:23 -0400
Received: (from jmg@localhost)
	by hydrogen.funkthat.com (8.12.9/8.11.6) id h6S5kkks090671;
	Sun, 27 Jul 2003 22:46:46 -0700 (PDT)
	(envelope-from jmg)
Date: Sun, 27 Jul 2003 22:46:46 -0700
From: John-Mark Gurney <gurney_j@efn.org>
To: Scott Long <scottl@freebsd.org>
Message-ID: <20030728054646.GR10708@funkthat.com>
Mail-Followup-To: Scott Long <scottl@freebsd.org>,
	freebsd-current@freebsd.org, Gary Jennejohn <garyj@jennejohn.org>,
	Mark Blackman <mark@exonetric.com>, Lukas Ertl <l.ertl@univie.ac.at>
References: <C882BF18-C03F-11D7-A23D-00039315D3FE@exonetric.com>
	<20030727163914.S698@korben.in.tern> <20030727191758.GN10708@funkthat.com>
	<3F24B5C6.4010403@freebsd.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3F24B5C6.4010403@freebsd.org>
User-Agent: Mutt/1.4.1i
X-Operating-System: FreeBSD 4.2-RELEASE i386
X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31  96 7A 22 B3 D8 56 36 F4
X-Files: The truth is out there
X-URL: http://resnet.uoregon.edu/~gurney_j/
X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html
cc: Gary Jennejohn <garyj@jennejohn.org>
cc: freebsd-current@freebsd.org
cc: Lukas Ertl <l.ertl@univie.ac.at>
cc: Mark Blackman <mark@exonetric.com>
Subject: Re: device driver memory leak in 5.1-20030726?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: John-Mark Gurney <gurney_j@efn.org>
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: Mon, 28 Jul 2003 05:46:52 -0000

Scott Long wrote this message on Sun, Jul 27, 2003 at 23:33 -0600:
> John-Mark Gurney wrote:
> 
> >It may be leaking, but it won't be leaking devbuf memory.  The only
> >thing that is in usb (in dev/usb) that uses M_DEVBUF is ukbd.
> 
> bus_dma_tag_create() allocates out of M_DEVBUF.  Could it be that tags
> are being created and never destroyed?

Ugh, yes, it does. :(  What is the point of having malloc areas if
everything uses them?   I just checked and about every driver allocates
memory under DEVBUF.  Is there some reason why we don't allocate more
malloc types to make this type of thing more easy to debug?

-- 
  John-Mark Gurney				Voice: +1 415 225 5579

     "All that I will do, has been done, All that I have, has not."