Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 5 Nov 2001 11:34:25 -0800
From:      Luigi Rizzo <rizzo@aciri.org>
To:        Mike Smith <msmith@freebsd.org>
Cc:        stable@freebsd.org
Subject:   Re: For review: preventing panics when unloading compiled-in modules
Message-ID:  <20011105113425.A76265@iguana.aciri.org>
In-Reply-To: <200111051936.fA5Ja3m03196@mass.dis.org>
References:  <20011105111839.A75789@iguana.aciri.org> <200111051936.fA5Ja3m03196@mass.dis.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Nov 05, 2001 at 11:36:03AM -0800, Mike Smith wrote:
> >     # kldload /ipfw.ko
> >  XX module_register: module ipfw already exists!
> >  XX linker_file_sysinit "ipfw.ko" failed to register! 17
> >     kldload: can't load /ipfw.ko: File exists
> >     # kldstat
> >     Id Refs Address    Size     Name
> >      1    2 0xc0000000 40000000 kernel
> >      2    1 0xc38aa000 8000     ipfw.ko
> >     # kldunload ipfw.ko
> >  XX linkerunload: attempt to unload file that was loaded by the kernel
> >     kldunload: can't unload file: Device busy
> > 
> > Technically, after the load, "ipfw.ko" is not a separate module,
> > so maybe one would like not to see it in the list. On the other
> > hand, the functionality associated with the module is present,
> > so this is not too bad...
> 
> It's bad, since you're listing the file as loaded when in fact it wasn't.

just to clarify, this is the same behaviour that we have right now.

> There's still confusion about the difference between a "file" (a loadable 
> object) and a "module".

yes, agreed. Good point.

	luigi

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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011105113425.A76265>