Re: [RELEASE] module-init-tools 0.8

[Tomas Szepe]

> > lsmod doesn't work at this point (hangs too, likely the same lock).
> > The deadlock prevents any further module loading (autofs, nfs and
> > others) and makes the system unusable.
> > 
> > Module debugging is next to impossible right now.  The apm.o module
> > oopses for me in 2.5.50.  ksymoops isn't able to translate any symbol
> > located in modules.  The in-kernel symbol decoder (CONFIG_KALLSYMS)
> > doesn't work too.
> 
> The new module stuff has been in for about three weeks now, many people
> are having problems with it, and I have yet to see a single post praising
> the *actual* benefits. Will there be a time when this is reverted and
> rescheduled for a future release (2.7?) or is this a do-or-die feature?
> 
> It doesn't have the feel of something solid having a few corner cases
> fixed, it feels like a bunch of band-aids which will unstick in future
> releases and continue to be high maintenence.

Also I can't see how the new module infrastructure could have made it
in w/o having been complete, *functional*, proven and thoroughly reviewed
off-tree in the first place (which I thought was pretty much a standard
around here).  Mature, drop-in replacement projects like Keith Owen's
kbuild 2.5 are getting ignored while something as wild as Rusty's "welcome
in module hell exhibit" is merged right when the tree is supposed to start
stabilizing.

And heck, I haven't even seen Viro and Hellwig complaining!
What's going on?  :)

-- 
Tomas Szepe <[e-mail]>