From: sashiko-bot@kernel.org
To: "Raul E Rangel" <rrangel@chromium.org>
Cc: linux-usb@vger.kernel.org
Subject: Re: [PATCH 2/6] usbip: vhci_hcd: complete unsent URBs locally in vhci_urb_dequeue()
Date: Wed, 21 Oct 2026 15:14:26 +0000 [thread overview]
Message-ID: <sashiko-outbox-180423@kernel.org> (raw)
In-Reply-To: <20261021150704.3129446-3-rrangel@chromium.org>
> When an URB is enqueued via vhci_urb_enqueue(), its vhci_priv entry is
> placed on vdev->priv_tx until vhci_tx_loop() moves it to vdev->priv_rx
> in dequeue_from_priv_tx() and sends USBIP_CMD_SUBMIT.
>
> If vhci_urb_dequeue() is called while the URB is still on vdev->priv_tx
> and vdev->ud.tcp_socket is non-NULL, vhci_urb_dequeue() currently sets
> urb->unlinked and queues a vhci_unlink entry on vdev->unlink_tx without
> removing the URB from vdev->priv_tx. This causes two bugs:
>
> 1. If vhci_tx_loop() has already exited after an earlier send error or
> been stopped during connection shutdown before tcp_socket is cleared,
> the URB remains on vdev->priv_tx. When vhci_device_unlink_cleanup()
> later runs pickup_urb_and_free_priv(), which only searches
> vdev->priv_rx, the vhci_unlink entry is freed while the URB remains
> linked on ep->urb_list with urb->unlinked set. Subsequent calls to
> [ ... ]
> Fixes: 258c81b341c8 ("usbip: give back URBs for unsent unlink requests during cleanup")
> Fixes: 04679b3489e0 ("Staging: USB/IP: add client driver")
> Cc: stable@vger.kernel.org
> Assisted-by: Gemini
> Signed-off-by: Raul E Rangel <rrangel@chromium.org>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261021150704.3129446-1-rrangel@chromium.org?part=2
next prev parent reply other threads:[~2026-10-21 15:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 15:06 [PATCH 0/6] usbip: vhci_hcd: fix URB giveback leaks and disconnect races Raul E Rangel
2026-10-21 15:06 ` [PATCH 1/6] usbip: vhci_hcd: protect urb->hcpriv with priv_lock in vhci_urb_dequeue() Raul E Rangel
2026-10-21 15:13 ` sashiko-bot
2026-10-21 15:06 ` [PATCH 2/6] usbip: vhci_hcd: complete unsent URBs locally " Raul E Rangel
2026-10-21 15:14 ` sashiko-bot [this message]
2026-10-21 15:06 ` [PATCH 3/6] usbip: vhci_hcd: stop enqueue and drain all pending URBs on disconnect Raul E Rangel
2026-10-21 15:22 ` sashiko-bot
2026-10-21 15:06 ` [PATCH 4/6] usbip: vhci_hcd: clear URB_DMA_MAP_SG on all giveback paths Raul E Rangel
2026-10-21 15:14 ` sashiko-bot
2026-10-21 15:07 ` [PATCH 5/6] usbip: vhci_hcd: allocate vhci_priv outside lock and handle ENOMEM Raul E Rangel
2026-10-21 15:16 ` sashiko-bot
2026-10-21 15:07 ` [PATCH 6/6] usbip: vhci_hcd: reject URBs from stale usb_device after port re-attach Raul E Rangel
2026-10-21 15:17 ` sashiko-bot
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-180423@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=rrangel@chromium.org \
--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