On Fri, 2009-06-26 at 09:56 -0400, Peter Jones wrote: > James, I think Chandra and I have responded to most if not all of your points, > and would appreciate your thoughts on what we've said. Well, you didn't respond to the important one: You're seeking to change the binding of these helpers from manual to automatic. This would mean that the modules are loaded in the single controller case, for which they may not be wanted and also when some multi path tool other than dm-mp is managing the device, in which case they may actively interfere with operations. Your basic contention is that you "don't see any concern here". When I ask what testing you've done for either of these, the studied silence eloquently illustrates "none". A policy change like this can't be made without being incredibly sure we're not going to screw up existing installations. The second point I made speaks to the technical ugliness of this: what you're basically doing is open coding multiple binding for a device handler specific case. If you can persuade me the policy above is correct, then technically all this should be done correctly via multiple binding in the generic device core ... before this interface nastiness you're constructing propagates outwards and becomes part of the user ABI. James -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html