From owner-freebsd-bugs  Mon May  8 21:17:24 2000
Delivered-To: freebsd-bugs@freebsd.org
Received: from implode.root.com (root.com [209.102.106.178])
	by hub.freebsd.org (Postfix) with ESMTP
	id 0FF6637B632; Mon,  8 May 2000 21:17:16 -0700 (PDT)
	(envelope-from dg@implode.root.com)
Received: from implode.root.com (localhost [127.0.0.1])
	by implode.root.com (8.8.8/8.8.5) with ESMTP id VAA20949;
	Mon, 8 May 2000 21:13:08 -0700 (PDT)
Message-Id: <200005090413.VAA20949@implode.root.com>
To: "Justin T. Gibbs" <gibbs@FreeBSD.ORG>
Cc: hoek@FreeBSD.ORG, rik@cronyx.ru, freebsd-bugs@FreeBSD.ORG
Subject: Re: kern/15763 
In-reply-to: Your message of "Mon, 08 May 2000 21:56:44 MDT."
             <200005090356.VAA05783@caspian.plutotech.com> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Mon, 08 May 2000 21:13:08 -0700
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

>>Synopsis: free() fails on contigmalloc() memory
>>
>>State-Changed-From-To: open->closed
>>State-Changed-By: hoek
>>State-Changed-When: Mon May 8 19:34:32 PDT 2000
>>State-Changed-Why: 
>>Don't do that.  The contigmalloc() function is only meant for limited
>>use, typically by drivers at boot time.  The free() function is meant
>>to work with malloc() not contigmalloc().
>
>How are you supposed to release contigmalloc'ed memory when
>a module unloads?  This is really a bug.

   You would normally use kmem_free() to free contigmalloc'ed memory.

-DG

David Greenman
Co-founder, The FreeBSD Project - http://www.freebsd.org
Creator of high-performance Internet servers - http://www.terasolutions.com
Pave the road of life with opportunities.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message