Mine was just a question from a non expert in kernel internals Bye 2018-03-22 18:29 GMT+01:00 Alan Stern <stern@xxxxxxxxxxxxxxxxxxx>: > On Thu, 22 Mar 2018, Menion wrote: > >> You are right. >> But what if usb-storage check if the deferred uas bind does not succeed? > > That is not possible, for two reasons. First, the kernel does not keep > track of binding attempts that fail. Second, the kernel can only try > to bind one driver to a device at a time. So if usb-storage tries to > bind first, it can't wait to see what will happen with uas -- because > nothing at all will happen until the usb-storage bind fails. > > It sounds like you're trying to figure out a bunch of far-out, overly > complex schemes to work around the fact that you simply didn't have the > right driver module present on your system. Wouldn't it be easier to > just fix your system than to try and complicate a kernel which already > is very complicated? > > In your case, the real problem was the missing kernel module. It seems > to me that you should have gotten an appropriate error message about > this somewhere -- perhaps in the system log. Was there such an error > message? If not, maybe one could be added. After all, if the kernel's > configuration indicates that a particular module was built, but it > can't be loaded, that definitely shows that something isn't working > right. > > Alan Stern > -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
