[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.44L0.1903281157070.1291-100000@iolanthe.rowland.org>
Date: Thu, 28 Mar 2019 11:57:44 -0400 (EDT)
From: Alan Stern <stern@...land.harvard.edu>
To: Oliver Neukum <oneukum@...e.com>
cc: Kento.A.Kobayashi@...y.com, <gregkh@...uxfoundation.org>,
<usb-storage@...ts.one-eyed-alien.net>, <Jacky.Cao@...y.com>,
<linux-kernel@...r.kernel.org>, <linux-scsi@...r.kernel.org>,
<linux-usb@...r.kernel.org>
Subject: Re: [PATCH] usb: uas: fix usb subsystem hang after power off hub
port
On Thu, 28 Mar 2019, Oliver Neukum wrote:
> On Do, 2019-03-28 at 07:53 +0000, Kento.A.Kobayashi@...y.com 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.
Alan Stern
Powered by blists - more mailing lists