Re: Plans for mISDN? Was: [PATCH 00/14] [ISDN] ...

From: Marcel Holtmann
Date: Thu Feb 21 2008 - 18:31:16 EST


Hi Andi,

that is not a big problem at all. If you have to enforce a specific
module load order then create some dummy exports like misdn_load() and
use them from the module that depends on it.

That's not necessarily enough. There are races during module load
when the next module is loaded already before the module it depends
on has finished initializing.

we were talking about the load order. This will solve the load order, but if we have races like the kind you described, then the whole mISDN design is broken. So if that is the fact, then my understanding is that we have too many modules. Simple combine the modules and use proper locking. More modules is not always better.

I regularly run into such a problem on my workstation with one
of the USB serial drivers for example. It errors out when autoloaded
during boot, but loads fine on retry later.

Report this to the USB mailing list.

Regards

Marcel

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/