From: Oliver Neukum <oneukum@suse.com>
To: Jiayi Li <lijiayi@kylinos.cn>, Oliver Neukum <oneukum@suse.com>
Cc: Alan Stern <stern@rowland.harvard.edu>,
Michal Pecio <michal.pecio@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, linux-scsi@vger.kernel.org,
usb-storage@lists.one-eyed-alien.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] usb: uas: wait for pending commands before unbinding
Date: Tue, 27 Oct 2026 15:35:34 +0100 [thread overview]
Message-ID: <8469d5fa-2f4e-4565-8d84-43d6b71b4a9c@suse.com> (raw)
In-Reply-To: <20261027131458.983241-1-lijiayi@kylinos.cn>
Hi,
On 27.10.26 14:14, Jiayi Li wrote:
> USB core normally disables interface endpoints before calling
> uas_disconnect(), cancelling URBs while the device may still be
> processing the associated commands. Some storage bridges may then
> fail to recover after a driver rebind and require a disconnect and
> reconnect.
[..]
I regret torturing you again, but there is a simple issue left.
> static void uas_disconnect(struct usb_interface *intf)
> {
> struct Scsi_Host *shost = usb_get_intfdata(intf);
> struct uas_dev_info *devinfo = (struct uas_dev_info *)shost->hostdata;
> unsigned long flags;
>
> + cancel_work(&devinfo->scan_work);
No _sync
> + spin_lock_irqsave(&shost->host_lock, flags);
> + scsi_block_requests(shost);
> + spin_unlock_irqrestore(&shost->host_lock, flags);
> +
> + uas_pre_disconnect(intf);
> +
> spin_lock_irqsave(&devinfo->lock, flags);
> devinfo->resetting = 1;
> spin_unlock_irqrestore(&devinfo->lock, flags);
>
> + scsi_unblock_requests(shost);
> +
> cancel_work_sync(&devinfo->work);
With _sync
I'd say both ought to use cancel_work_sync()
Regards
Oliver
next prev parent reply other threads:[~2026-10-27 14:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 13:14 [PATCH v3] usb: uas: wait for pending commands before unbinding Jiayi Li
2026-10-27 13:26 ` sashiko-bot
2026-10-27 14:35 ` Oliver Neukum [this message]
2026-10-28 2:09 ` Jiayi Li
2026-10-28 8:48 ` Oliver Neukum
2026-10-28 9:21 ` Jiayi Li
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8469d5fa-2f4e-4565-8d84-43d6b71b4a9c@suse.com \
--to=oneukum@suse.com \
--cc=gregkh@linuxfoundation.org \
--cc=lijiayi@kylinos.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=michal.pecio@gmail.com \
--cc=stern@rowland.harvard.edu \
--cc=usb-storage@lists.one-eyed-alien.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox