From: sashiko-bot@kernel.org
To: "Oliver Neukum" <oneukum@suse.com>
Cc: linux-usb@vger.kernel.org
Subject: Re: [PATCH] usb: uas: do not leak error codes from usb_alloc_streams()
Date: Thu, 08 Oct 2026 13:45:48 +0000 [thread overview]
Message-ID: <sashiko-outbox-164241@kernel.org> (raw)
In-Reply-To: <20261008132711.211908-1-oneukum@suse.com>
> While a UAS device is undergoing a reset not triggered by
> the SCSI layer there is a short window in the error case
> of reallocating streams during which internal error codes
> of the USB layer are exported as nonsensical queue depths.
>
> The error has been noticed by Sashiko in a different
> context, but it is a general issue.
>
> Fixes: 4de7a3735bdc4 ("uas: Fix reset handling for externally triggered reset")
> Signed-off-by: Oliver Neukum <oneukum@suse.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261008132711.211908-1-oneukum@suse.com?part=1
next prev parent reply other threads:[~2026-10-08 13:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-08 13:27 [PATCH] usb: uas: do not leak error codes from usb_alloc_streams() Oliver Neukum
2026-10-08 13:45 ` sashiko-bot [this message]
2026-10-08 16:23 ` Sergey Shtylyov
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=sashiko-outbox-164241@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=oneukum@suse.com \
--cc=sashiko-reviews@lists.linux.dev \
/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