HEADS UP: Beware of dragons in module loader code!

[Peter Wemm]

On Monday 17 May 2004 03:37 pm, Peter Wemm wrote:
> On Monday 17 May 2004 02:31 pm, Peter Wemm wrote:
> > On Sunday 16 May 2004 06:36 pm, Peter Wemm wrote:
> > > I've committed the support changes and enabled the new module
> > > loader, but beware!  It does still blow up!  Consequently, I did
> > > *NOT* remove the 'NO_MODULES' override in GENERIC etc because
> > > there are a number of system daemons that will try and load
> > > things during startup.  If this suddenly started loading modules,
> > > it Would Be A Bad Thing.
> > >
> > > On an unrelated note, I could really use some eyes looking at the
> > > sys/kern/link_elf_obj.c file.  Somewhere, I have a bug (or a
> > > series of bugs) that is causing significant memory trashing.
> >
> > Turns out that there were multiple bugs, some in my code (which I
> > fixed as a side effect of something else), and the big one was in
> > the kernel linker itself (not my bug! :-).
> >
> > Anyway, the guts of kldload(8) support is there now.  Now for
> > kldxref(8) and loader(8).  Whee.
>
> Beware, I've turned modules on for GENERIC and NOTES.  I've tested a
> couple of things including:  usb, ums (for dependency test on usb),
> vinum, md and a dummy test module.
>
> oops. Footnote.  sound just blew up for me.  Anyway, I've left it all
> turned on for the moment.

I believe this last gotcha! is fixed now too.
-- 
Peter Wemm - peter at wemm.org; peter at FreeBSD.org; peter at yahoo-inc.com
"All of this is for nothing if we don't go to the stars" - JMS/B5