Hello, Rob. On Thu, Oct 27, 2016 at 01:55:19PM -0500, Rob Herring wrote: > Seems like this is mixing async drv probe and async scsi scan and the > problem is in the latter? I don't think async drv probe should have > any problems. If a driver probe starts some async operation, then it > seems to me that it is its responsibility to wait for completion in > remove(). I'm not sure about that. The async operation synchronization isn't per-driver or module. Both during boot and module operations, they're synchronized globally, which makes sense given its purpose and that's also why we don't see these brekages without this debug option. It doesn't make sense to me to add a whole new set of behaviors just for a debug option. Thanks. -- tejun -- To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
