On Thu, 28 Mar 2019, Oliver Neukum wrote: > On Do, 2019-03-28 at 11:57 -0400, Alan Stern wrote: > > On Thu, 28 Mar 2019, Oliver Neukum wrote: > > > > > On Do, 2019-03-28 at 07:53 +0000, Kento.A.Kobayashi@xxxxxxxx wrote: > > > > Hi, > > > > > > > > > Sorry, > > > > > > > > > > I thought this was clear. Your patch is making the assumption that the reset is triggered by the SCSI layer. You cannot make that assumption, as there is an ioctl for resetting a USB device. > > > > > In case we are getting an error during the reset (our endpoints vanish), the device driver must report that to the USB layer, so the driver will always be disconnected. > > > > > We cannot drop errors. > > > > > > > > > > Regards > > > > > Oliver > > > > > > > > This patch modified uas_post_reset to skip rebind operation to avoid exception while -ENODEV happens not drop error. > > > > If uas_post_reset happens -ENODEV, usb_reset_and_verify_device must happen error. > > > > So,when we use ioctl(USBDEVFS_RESET) to reset device, if usb_reset_and_verify_device happens error, the error will be reported through ioctl return value. > > > > > > OK, It is possible that I am stupid. We must rebind if uas_post_reset() > > > fails. The driver will crash without the endpoints. Can you please > > > explain again in greater detail, what you are trying to achieve? > > > > Actually no, the driver doesn't have to do anything if the post-reset > > method fails. usbcore will take care of rebinding automatically. > > Yes, but the rebinding is not optional. Hence, either the post_reset() > must fail to trigger it, or it will be triggered anyway. > So if the rebinding hangs the machine, I cannot see how alter > changing the return value of uas_post_reset() would help. > > It looks to me like the state transitions of SCSI are too > restrictive. Maybe I don't understand the problem correctly. It sounds like the problem occurs because uas tries to rebind (Where, how, and why does it do this? I don't see anything special in uas_post_reset) using the same scsi_host structure as before instead of creating a new one. Trying to reuse a defunct host is definitely not allowed. But if uas didn't try to do anything special, it would be unbound from the device, causing the scsi_host to be destroyed. Then when usbcore automatically attempted a rebind, uas would create a new scsi_host and the rebind would have a chance to succeed, without hanging anything. If this description is wrong, please explain more fully. Alan Stern
