On Mon, Jul 26, 2010 at 06:41:11AM +1000, matthew green wrote: > it seems to me the root problem is that module_mutex is held while > calling into the module startup routines.
Here is one related question: is it ensured that the module lock is dropped immediately after a modular device driver returns from its attachment routine? I am thinking of a case where a modular driver defers its configuration by using config_interrupts(9) or config_finalize_register(9). - Jukka.