All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Raul E Rangel" <rrangel@chromium.org>
Cc: linux-usb@vger.kernel.org
Subject: Re: [PATCH 5/6] usbip: vhci_hcd: allocate vhci_priv outside lock and handle ENOMEM
Date: Wed, 21 Oct 2026 15:16:27 +0000	[thread overview]
Message-ID: <sashiko-outbox-180427@kernel.org> (raw)
In-Reply-To: <20261021150704.3129446-6-rrangel@chromium.org>

> In vhci_urb_enqueue(), usb_hcd_link_urb_to_ep() links the URB onto the
> endpoint before calling vhci_tx_urb(), which allocates struct vhci_priv
> with GFP_ATOMIC while holding vhci->lock. If that allocation fails,
> vhci_tx_urb() triggers VDEV_EVENT_ERROR_MALLOC and returns while
> vhci_urb_enqueue() still returns 0, leaving urb->hcpriv NULL and the URB
> linked on ep->urb_list where vhci_urb_dequeue() rejects it with -EIDRM.
> Moreover, failing a single URB submission should return -ENOMEM to the
> caller rather than tearing down the entire USB/IP connection.
> 
> Allocate struct vhci_priv in vhci_urb_enqueue() using the caller's
> mem_flags before acquiring vhci->lock, pass it to vhci_tx_urb(), and
> free it on early-exit and non-transmit paths.
> 
> In vhci_urb_dequeue(), if allocating struct vhci_unlink fails after
> usb_hcd_check_unlink_urb() has already marked urb->unlinked, return 0
> after triggering VDEV_EVENT_ERROR_MALLOC so callers know the unlink was
> accepted and connection teardown will drain priv_rx and give back the
> URB.
> 
> 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=5


  reply	other threads:[~2026-10-21 15:16 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
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 [this message]
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-180427@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.