From: Sarthak Kukreti <sarthakkukreti@google.com>
To: Oliver Neukum <oneukum@suse.com>,
Alan Stern <stern@rowland.harvard.edu>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"James E . J . Bottomley"
<James.Bottomley@HansenPartnership.com>,
"Martin K . Petersen" <mkp@kernel.org>
Cc: linux-usb@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org,
Sarthak Kukreti <sarthakkukreti@google.com>
Subject: [PATCH v2 0/3] usb: uas / scsi: fail inflight and queued commands on dead links
Date: Thu, 12 Nov 2026 18:49:18 -0800 [thread overview]
Message-ID: <20261113024922.27977-1-sarthakkukreti@google.com> (raw)
Unplugging a UAS device during system suspend after hub_wq is frozen
defers usb_disconnect() until hub_wq thaws. When sd_suspend_system()
issues SYNCHRONIZE_CACHE to the disconnected target:
1. If the HCD accepts the URBs, the status URB fails in uas_stat_cmplt()
without completing the command, stranding SYNCHRONIZE_CACHE for the
60s SCSI timeout and triggering the 25s DPM watchdog. Patch 1 tracks
the active sense_urb per command and completes the owning command in
uas_stat_cmplt() on status URB failure while unlinking any inflight
data URBs.
2. If usb_submit_urb() fails with -ESHUTDOWN, -ENOENT, or -EHOSTUNREACH,
uas_queuecommand_lck() requeues the command instead of failing it,
and leaks unsubmitted URBs or orphans already-submitted URBs on
partial submission failure. Patch 2 fails the command with
DID_NO_CONNECT, frees unsubmitted URBs, and unlinks any submitted
status or data URBs.
3. When the command completes with DID_NO_CONNECT,
scsi_check_passthrough() matches SCMD_FAILURE_RESULT_ANY and retries
it against the disconnected target. Patch 3 skips retries on
DID_NO_CONNECT, DID_BAD_TARGET, and DID_TRANSPORT_FAILFAST.
Tested using a USB/IP (vhci_hcd) UAS target emulator that freezes
hub_wq, injects -EPROTO on the status URB during inflight
SYNCHRONIZE_CACHE and READ(10) commands, and verifies immediate
completion without DPM watchdog timeouts, along with the scsi_lib KUnit
test suite.
Changes in v2:
- Track sense_urb in uas_cmd_info and complete only the command owning
the failed status URB in uas_stat_cmplt() instead of looping across
all devinfo->cmnd[] slots and orphaning other commands' sense URBs.
- Set DID_NO_CONNECT only on -ENODEV and -ESHUTDOWN in uas_stat_cmplt()
and uas_data_cmplt(), and DID_ERROR on other status/data URB errors.
- Clear pending submit and work flags and free unsubmitted URBs when
completing commands on status URB or partial submission failure.
- Unlink already-submitted status and data URBs in
uas_queuecommand_lck() when a later URB submission fails, and remove
the unused out label.
- Add Fixes tags to all three patches.
v1:
https://lore.kernel.org/r/20261113003536.3622755-1-sarthakkukreti@google.com
Sarthak Kukreti (3):
usb: uas: complete command on status URB error
usb: uas: fail command submission on fatal USB errors
scsi: core: do not retry passthrough requests on disconnected targets
drivers/scsi/scsi_lib.c | 5 ++
drivers/scsi/scsi_lib_test.c | 9 ++-
drivers/usb/storage/uas.c | 128 +++++++++++++++++++++++++++++------
3 files changed, 122 insertions(+), 20 deletions(-)
--
2.56.0.611.g1030f0b940-goog
next reply other threads:[~2026-11-13 2:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 2:49 Sarthak Kukreti [this message]
2026-11-13 2:49 ` [PATCH v2 1/3] usb: uas: complete command on status URB error Sarthak Kukreti
2026-11-13 2:49 ` [PATCH v2 2/3] usb: uas: fail command submission on fatal USB errors Sarthak Kukreti
2026-11-13 2:49 ` [PATCH v2 3/3] scsi: core: do not retry passthrough requests on disconnected targets Sarthak Kukreti
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=20261113024922.27977-1-sarthakkukreti@google.com \
--to=sarthakkukreti@google.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mkp@kernel.org \
--cc=oneukum@suse.com \
--cc=stern@rowland.harvard.edu \
/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
all inboxes | Powered by JetHome®