From owner-freebsd-bugs  Mon May  8 20:56:50 2000
Delivered-To: freebsd-bugs@freebsd.org
Received: from caspian.plutotech.com (caspian.plutotech.com [206.168.67.80])
	by hub.freebsd.org (Postfix) with ESMTP
	id B278D37BD5F; Mon,  8 May 2000 20:56:47 -0700 (PDT)
	(envelope-from gibbs@caspian.plutotech.com)
Received: from caspian.plutotech.com (localhost [127.0.0.1])
	by caspian.plutotech.com (8.9.3/8.9.1) with ESMTP id VAA05783;
	Mon, 8 May 2000 21:56:44 -0600 (MDT)
	(envelope-from gibbs@caspian.plutotech.com)
Message-Id: <200005090356.VAA05783@caspian.plutotech.com>
X-Mailer: exmh version 2.1.1 10/15/1999
To: hoek@FreeBSD.ORG
Cc: rik@cronyx.ru, freebsd-bugs@FreeBSD.ORG
Subject: Re: kern/15763 
In-Reply-To: Your message of "Mon, 08 May 2000 19:38:21 PDT."
             <200005090238.TAA47598@freefall.freebsd.org> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 08 May 2000 21:56:44 -0600
From: "Justin T. Gibbs" <gibbs@FreeBSD.org>
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.

--
Justin



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