Re: [PATCH v2] usb: uas: quiesce SCSI before stopping endpoints on unbind

[Jiayi Li]

Hi Oliver,

> Acked-by: Oliver Neukum <oneukum@xxxxxxxx>

Thank you for the Acked-by. Subsequent testing found a regression in
v2: physically unplugging the device with UAS commands in flight can
cause an approximately 30-second SCSI timeout. I described the failure
in my reply to the Sashiko review:

https://lore.kernel.org/linux-scsi/20260922100542.164047-1-lijiayi@xxxxxxxxxx/

I have a local candidate that keeps the unified teardown order.
When URB submission or completion returns -ENODEV or -ESHUTDOWN,
it marks the transport dead, stops further submissions, clears
COMMAND_INFLIGHT and sets DID_NO_CONNECT for pending commands.
It drains the remaining URBs in work context, allowing the commands
to complete through uas_try_complete().

Does this approach seem reasonable, or would you suggest a simpler
way to handle the physical-disconnect case?

Thanks,
Jiayi