[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AE5419EAB4965843B3C0C1FE29F1FFE5899C80@JPYOKXMS103.jp.sony.com>
Date: Mon, 15 Apr 2019 00:27:43 +0000
From: <Kento.A.Kobayashi@...y.com>
To: <stern@...land.harvard.edu>, <bvanassche@....org>
CC: <martin.petersen@...cle.com>, <jejb@...ux.ibm.com>,
<oneukum@...e.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
Hi
>The unbind happens from inside the SCSI EH callback. If that really is not allowed, we'll need to change it. Or we can just change it regardless, since the effort required is pretty small.
>
>Kento, please try the patch below. Does it help with your problem?
Thank you for suggestion about this problem.
I confirmed your patch fixes this problem.
I think you change policy for error handler to not calling unbind, right?
In addition, I have a question about this patch.
Could you please tell me why it should not be allowed that the unbind is occurred from eh callback?
This patch will ignore all error which is returned from usb_reset_and_verify_device.
But my patch will ignore error only being returned ENODEV case.
I think side effect of your patch is bigger than my patch.
So I want to know why the unbind is occurred from eh callback should not be allowed.
Regards,
Kento Kobayashi
Powered by blists - more mailing lists