On Fri, 2015-10-02 at 15:34 +0200, Christoph Hellwig wrote: > On Fri, Oct 02, 2015 at 06:25:01AM -0700, James Bottomley wrote: > > That doesn't matter: if you modprobe alua after all devices are > > discovered, it will attach correctly to all potential devices from the > > alua module_init. This means the effect is the same whether the > > request_module is sync or async ... the object is to get the device > > attached to alua if it is an alua device. > > No, in 4.3-rc it won't. We removed that feature.
I think I prefer restoring that to having to build in every dh module to get them to work. If we take your proposed fix for the sync module load in the current scheme, any non-built in modules would never attach, so we'd be moving towards the conclusion that *every* device handler has to be non-modular. Skimming the code it looks like dh should be using the driver binding model rather than reinventing it. That would decouple it better and make sure binding happened regardless of when the module was loaded. 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
