From owner-freebsd-net  Wed Nov 15  0:35:46 2000
Delivered-To: freebsd-net@freebsd.org
Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11])
	by hub.freebsd.org (Postfix) with SMTP id 3A70237B4C5
	for <freebsd-net@freebsd.org>; Wed, 15 Nov 2000 00:35:43 -0800 (PST)
Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP
          id <aa94058@salmon>; 15 Nov 2000 08:35:41 +0000 (GMT)
To: Julian Elischer <julian@elischer.org>
Cc: Bosko Milekic <bmilekic@dsuper.net>,
	David Malone <dwmalone@maths.tcd.ie>, iedowse@maths.tcd.ie,
	freebsd-net@freebsd.org, dwmalone@maths.tcd.ie
Subject: Re: M_RDONLY: review & comment 
In-reply-to: Your message of "Tue, 14 Nov 2000 04:39:54 PST."
             <3A11329A.D54E17E3@elischer.org> 
X-Request-Do: 
Date: Wed, 15 Nov 2000 08:35:40 +0000
From: David Malone <dwmalone@maths.tcd.ie>
Message-ID:  <200011150835.aa94058@salmon.maths.tcd.ie>
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

> using char * is unsafe if the aim is to tag mbufs that were allocated 
> by some module, if the midule is unloaded..
> (the mbufs may hang around in some queu way afte the module has gone..
> and an attempt to follow the char 8 pointer......)

If a module which is responsible for mbufs with external storage,
then the free function for that storage will be in the module. If,
after the module is unloaded, mbufs are still allocated which are
using this external storage things will blow up when they are freed.

So if the free function is still there, so will what the char *
points at. (Unless I'm missing something...)

	David.


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