On Wed, 5 Mar 2008, Frank Ch. Eigler wrote: > > There's a theoretical potential for the system to crash in -rt when > > unloading a module. Simply because interrupts are threads. > > > > Some device has an interrupt handler that is called and preempted. > > At that moment the module for that device is unloaded. [...] > > Since the code for the interrupt handler no longer exists... KABOOM! > > Perhaps you can identify those modules that have asked for interrupts, > and block only them from unloading. Or, would it be outrageously > expensive to increment the module refcount while one of its interrupt > handlers is running? Actually, we were simply thinking of calling an rcu_lock before checking the handlers, and releasing the lock when all are done. Then before doing the module unload, we do a rcu_sync. Note, no interrupt handler should ever do a rcu_sync. -- Steve -- To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
