On Sun, 6 January 2008 14:11:47 -0500, Erez Zadok wrote: > > The problem appears to be an interaction of two components--module loading > and lockdep--that's perhaps why it wasn't given enough attention.
Correct. For modules lockdep depends on initializations done after module_init has finished. However block2mtd is an odd sod that can call into lockdep code during module_init, causing the bug you noticed. Several solutions are possible. Modules could get two initcalls, one to decide whether module load should get aborted, the other run later, after the remaining module initializations are done. Or the module loader could always do the initializations and revoke them later, if module_init failed. But I personally am too unfamiliar with the module code to trust my judgement and have yet to receive feedback. Even you seem to ignore my mails and not even Cc: me later on. I must have done something really horrible in my last life, it seems. Jörn -- A quarrel is quickly settled when deserted by one party; there is no battle unless there be two. -- Seneca -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
