On Wed, 2015-09-30 at 17:53 -0400, Tejun Heo wrote: > Hello, Christoph. > > On Wed, Sep 30, 2015 at 05:14:49PM +0200, Christoph Hellwig wrote: > > The problem is that async probing deadlocks vs a synchronous > > request_module, as Tejun figured out based on the thrad in > > http://thread.gmane.org/gmane.linux.kernel/1420814 > > > > Tejun, if I understand the thread and your patch right there really > > isn't any good altenative to a synchronous request_module, and you > > thus disabled autoloading elevator modules, right? > > Yeap, that's right. IIRC, the conclusion was "let's not do that".
Perhaps we don't have to be that draconian. There's no real reason we can't autoload asynchronously. If the module isn't ready by the time we come to check the attachment, then it will attach to the device later when the module init routine runs. Should we do anything to limit the module_request floods? This will likely happen for every LUN of an ALUA system ... there can be hundreds of those. James -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
