[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <yq1a7h0orn8.fsf@oracle.com>
Date: Mon, 08 Apr 2019 22:10:19 -0400
From: "Martin K. Petersen" <martin.petersen@...cle.com>
To: Alan Stern <stern@...land.harvard.edu>
Cc: Kento.A.Kobayashi@...y.com,
"James E.J. Bottomley" <jejb@...ux.ibm.com>,
"Martin K. Petersen" <martin.petersen@...cle.com>,
Oliver Neukum <oneukum@...e.com>, <gregkh@...uxfoundation.org>,
USB Storage list <usb-storage@...ts.one-eyed-alien.net>,
<Jacky.Cao@...y.com>,
Kernel development list <linux-kernel@...r.kernel.org>,
SCSI development list <linux-scsi@...r.kernel.org>,
USB list <linux-usb@...r.kernel.org>
Subject: Re: [PATCH] usb: uas: fix usb subsystem hang after power off hub port
Alan,
> So it looks as though the SCSI subsystem doesn't like to have a reset
> handler call scsi_remove_host.
Are you talking about a PCI device removal handler or a SCSI error
handler?
> Commands dispatched by the removal routines are forced to wait for the
> reset recovery to finish, which won't happen until those commands have
> been completed.
>
> Is this a bug in the SCSI core? If not, we need to know what is the
> right way to do things when a reset handler detects that the SCSI host
> has been hot-unplugged.
PCI surprise removal should generally work. But it's somewhat unusual
for a SCSI host to evaporate in the middle of error handling. After all,
the main purpose of eh is to leverage the interfaces provided by the
host to try to reconnect to a target that tripped and fell off the
bus...
--
Martin K. Petersen Oracle Linux Engineering
Powered by blists - more mailing lists