All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Pecio <michal.pecio@gmail.com>
To: Mathias Nyman <mathias.nyman@linux.intel.com>
Cc: <gregkh@linuxfoundation.org>, <linux-usb@vger.kernel.org>,
	regressions@lists.linux.dev, Yiyu Zhou <yiyu@yiyuzhou.io>,
	Dennis Wissel <dennis@dsine.de>
Subject: Re: [PATCH v2] xhci: give back TDs and clean up ep0 after disconnect
Date: Sat, 31 Oct 2026 05:06:03 +0100	[thread overview]
Message-ID: <20261031050603.6067d2e5.michal.pecio@gmail.com> (raw)
In-Reply-To: <20261029204324.658845-2-mathias.nyman@linux.intel.com>

On Thu, 29 Oct 2026 22:43:24 +0200, Mathias Nyman wrote:
> From: Yiyu Zhou <yiyu@yiyuzhou.io>
> 
> Fix a regression in v7.3 introduced by the commits in the Fixes tags.
> Those patches avoid endpoint recovery and rapid state changes after
> the root port link is lost.
> 
> This caused a regression in device enumeration.
> 
> It turns out that a subset of USB HID devices briefly disconnect during
> enumeration. USB core manages to resuscitate these devices without
> reallocating them, and thus continue using the same udev, xhci vdev and
> default control endpoint (ep0) of the device.
> xhci didn't give back or clean up halted TDs behind disconnected ports
> as it assumed that the disconnect cancels all URBs, and drops and frees
> all endpoints.
> 
> This is not the case, so cancel and give back TDs on halted endpoint
> behind disconnected ports, make sure ep0 is cleared and in a proper state
> to continue working even after a link error or disconnect is detected.
> Also prevent new URBs until device is reset.
> 
> One issue related to the TDs not being given back was seen on a PFU
> HHKB Professional HYBRID Type-S keyboard (04fe:0021).
> It drops off the bus about 300 ms after its first enumeration, while
> usbhid is still probing its third interface. The probe runs in hub_wq,
> so the disconnect is not handled until the probe returns.
> On a root port the HID descriptor request and its four retries in
> hid_get_class_descriptor() each wait for the full 5 second
> USB_CTRL_GET_TIMEOUT:
> 
>   [57685.006036] usb 3-2: new full-speed USB device number 24 using xhci_hcd
>   ...
>   [57685.291304] hid-generic 0003:04FE:0021.0017: input,hidraw1: USB HID v1.11 Keyboard [PFU Limited HHKB-Hybrid] on usb-0000:00:14.0-2/input1
>   [57711.221083] usbhid 3-2:1.2: can't add hid device: -110
>   [57711.221613] usbhid 3-2:1.2: probe with driver usbhid failed with error -110
>   [57711.221842] usb 3-2: USB disconnect, device number 24
> 
> [mn: merge EP_DROP_PENDING and link_inactive checks in xhci_urb_enqueue(),
>  return TDs and clean up ep0 on disconnect, rewrite commit message]
> 
> Fixes: 042aad8d0db6 ("xhci: prevent endpoint recovery after roothub disconnect")
> Fixes: 7e0ef4332ed9 ("xhci: avoid xHC endpoint changes after disconnect or link error.")
> Closes: https://lore.kernel.org/all/20261010071811.20483-1-yiyu@yiyuzhou.io/
> Closes: https://lore.kernel.org/linux-usb/4MjB9K-2SoiA85WbI9iEig@dsine.de/
> Tested-by: Yiyu Zhou <yiyu@yiyuzhou.io>
> Tested-by: Dennis Wissel <dennis@dsine.de>
> Signed-off-by: Yiyu Zhou <yiyu@yiyuzhou.io>
> Co-developed-by: Mathias Nyman <mathias.nyman@linux.intel.com>
> Signed-off-by: Mathias Nyman <mathias.nyman@linux.intel.com>
> ---
> 
>  v2 changes:
>  - rebase on usb-linus
>  - remove Assisted-by: LLM as suggested by latest checkpatch
> 
>  drivers/usb/host/xhci-ring.c | 73 ++++++++++++++++++++++++++++++------
>  drivers/usb/host/xhci.c      | 13 ++++---
>  2 files changed, 69 insertions(+), 17 deletions(-)
> 
> diff --git a/drivers/usb/host/xhci-ring.c b/drivers/usb/host/xhci-ring.c
> index c23434001e9c..a1fa188680f5 100644
> --- a/drivers/usb/host/xhci-ring.c
> +++ b/drivers/usb/host/xhci-ring.c
> @@ -65,6 +65,7 @@
>  static int queue_command(struct xhci_hcd *xhci, struct xhci_command *cmd,
>  			 u32 field1, u32 field2,
>  			 u32 field3, u32 field4, bool command_must_succeed);
> +static void xhci_kill_endpoint_urbs(struct xhci_hcd *xhci, int slot_id, int ep_index);
>  
>  /*
>   * Returns zero if the TRB isn't in this segment, otherwise it returns the DMA
> @@ -962,6 +963,24 @@ static void xhci_giveback_invalidated_tds(struct xhci_hcd *xhci, struct xhci_vir
>  	}
>  }
>  
> +static void xhci_cancel_ring_tds(struct xhci_hcd *xhci, struct xhci_virt_ep *ep,
> +				 struct xhci_ring *ring, int td_status)
> +{
> +	struct xhci_td *tmp_td;
> +	struct xhci_td *td;
> +
> +	/* Add all TDs on ring to cancelled td list */
> +	list_for_each_entry_safe(td, tmp_td, &ring->td_list, td_list) {
> +		if (list_empty(&td->cancelled_td_list)) {
> +			list_add_tail(&td->cancelled_td_list,
> +				      &ep->cancelled_td_list);
> +			td->cancel_status = TD_DIRTY;
> +			if (!td->status)
> +				td->status = td_status;
> +		}
> +	}
> +}
> +
>  static int xhci_reset_halted_ep(struct xhci_hcd *xhci, unsigned int slot_id,
>  				unsigned int ep_index, enum xhci_ep_reset_type reset_type)
>  {
> @@ -993,25 +1012,53 @@ static int xhci_handle_halted_endpoint(struct xhci_hcd *xhci,
>  {
>  	struct xhci_port *rhub_port = ep->vdev->rhub_port;
>  	unsigned int slot_id = ep->vdev->slot_id;
> +	bool disconnected = false;
> +	struct xhci_ring *ring;
>  	int err;
>  
> -	/*
> -	 * Avoid resetting endpoint if link is inactive or device disconnected.
> -	 * Can cause host hang.
> -	 * Device will be reset to recover an inactive link, so don't do anything
> -	 */
> +	/* link is inactive or device disconnected */
>  	if (rhub_port->link_inactive || !rhub_port->connected) {
>  		ep->ep_state |= EP_DROP_PENDING;
> -		return -ENODEV;
> +		disconnected = true;
> +		if (!td && ep->ep_index != 0) {
> +			xhci_kill_endpoint_urbs(xhci, slot_id, ep->ep_index);
> +			return -ENODEV;
> +		}

The duplicate xhci_kill_endpoint_urbs() call wouldn't be necessary if
the later code which also calls it could handle this edge case.

(And my patch showed how 'disconnected' variable can be omitted too.)

>  	}
>  
> -	/* add td to cancelled list and let reset ep handler take care of it */
> -	if (reset_type == EP_HARD_RESET) {
> -		ep->ep_state |= EP_HARD_CLEAR_TOGGLE;
> +	/* Add halted td to cancelled list and let reset ep handler take care of it */
> +	if (reset_type == EP_HARD_RESET || disconnected) {
>  		if (td && list_empty(&td->cancelled_td_list)) {
>  			list_add_tail(&td->cancelled_td_list, &ep->cancelled_td_list);
>  			td->cancel_status = TD_HALTED;
> +			if (disconnected && !td->status)
> +				td->status = -EPROTO;

That's confusing (speaking from experience, heh). It could simply be

  if (reset_type == EP_SOFT_RESET)

because that's the only valid reason for td->status being 0 here.

> +		}
> +	}
> +
> +	/*
> +	 * Avoid resetting non-ep0 endpoints if link is inactive or device
> +	 * disconnected. Can cause host hang.
> +	 * Endpoints other than ep0 won't restart before the device is reset or
> +	 * the endpoint is dropped, so cancel all TDs, and give back non-ep0 TDs
> +	 * now instead of letting them time out. Ep0 can survive a short device
> +	 * disconnect during enumeration so reset ep0 normally and clean it up.

I don't think this is limited to enumeration. Indeed, probe() is not
enumeration. I see no reason why the same can't happen at any time.

> +	 */
> +	if (disconnected) {
> +		ring = td ? xhci_urb_to_transfer_ring(xhci, td->urb) : ep->ring;
> +		xhci_cancel_ring_tds(xhci, ep, ring, -ESHUTDOWN);

So that's why we bail out on (!td && ep->ep_index != 0) several lines
prior, to avoid NULL dereference. A bit complicated, this may work too:

  if (ring)
	xhci_cancel_ring_tds(...)

I think it's harmless that we could then call xhci_cancel_ring_tds()
and  xhci_process_cancelled_tds() on non-zero endpoints sometimes?
Stop EP handler also calls that stuff after setting EP_DROP_PENDING.

What Stop EP fails to do is giving back stranded URBs after setting
EP_DROP_PENDING. I have suggested how this can be done by simply
moving this code added here to elsewhere.

> +		if (ep->ep_index != 0) {
> +			xhci_dbg(xhci, "Not resetting ep %u slot %u after disconnect\n",
> +				 ep->ep_index, slot_id);
> +
> +			xhci_process_cancelled_tds(xhci, ep);
> +			xhci_kill_endpoint_urbs(xhci, slot_id, ep->ep_index);
> +			return -ENODEV;
>  		}
> +		/* hard-reset a halted disconnected ep0 */
> +		xhci_dbg(xhci, "Reset and clean up ep0 slot %u after disconnect\n",
> +			 slot_id);
> +		reset_type = EP_HARD_RESET;
>  	}
>  
>  	if (ep->ep_state & EP_HALTED) {
> @@ -1020,6 +1067,9 @@ static int xhci_handle_halted_endpoint(struct xhci_hcd *xhci,
>  		return 0;
>  	}
>  
> +	if (reset_type == EP_HARD_RESET)
> +		ep->ep_state |= EP_HARD_CLEAR_TOGGLE;

Wasted opportunity to place this after actually queuing the command,
which is the only place it really belongs.

> +
>  	err = xhci_reset_halted_ep(xhci, slot_id, ep->ep_index, reset_type);
>  	if (err)
>  		return err;
> @@ -1070,8 +1120,9 @@ static int xhci_invalidate_cancelled_tds(struct xhci_hcd *xhci, struct xhci_virt
>  			continue;
>  		}
>  
> -		/* device disconnected or link error, ep will be dropped */
> -		if (ep->ep_state & EP_DROP_PENDING) {
> +		/* device disconnected or link error, non-ep0 endpoints will be dropped */
> +		if (ep->ep_state & EP_DROP_PENDING && ep->ep_index != 0) {
> +			td_to_noop(xhci, ep, td, false);
>  			td->cancel_status = TD_CLEARED;
>  			continue;

I don't like this growth of special cases and duplication in the big
loop over cancelled_td_list. Although my attempt at eliminting it did
have an issue, there has to be a better way...

>  		}
> diff --git a/drivers/usb/host/xhci.c b/drivers/usb/host/xhci.c
> index 30ac1bc4559b..b50a582be1fb 100644
> --- a/drivers/usb/host/xhci.c
> +++ b/drivers/usb/host/xhci.c
> @@ -1665,12 +1665,6 @@ static int xhci_urb_enqueue(struct usb_hcd *hcd, struct urb *urb, gfp_t mem_flag
>  		goto free_priv;
>  	}
>  
> -	if (xhci->devs[slot_id]->rhub_port->link_inactive) {
> -		xhci_dbg(xhci, "Can't queue urb, port error, link inactive\n");
> -		ret = -ENODEV;
> -		goto free_priv;
> -	}
> -
>  	if (xhci->xhc_state & XHCI_STATE_DYING) {
>  		xhci_dbg(xhci, "Ep 0x%x: URB %p submitted for non-responsive xHCI host.\n",
>  			 urb->ep->desc.bEndpointAddress, urb);
> @@ -1680,6 +1674,13 @@ static int xhci_urb_enqueue(struct usb_hcd *hcd, struct urb *urb, gfp_t mem_flag
>  
>  	ep_state = &xhci->devs[slot_id]->eps[ep_index].ep_state;
>  
> +	if (xhci->devs[slot_id]->rhub_port->link_inactive ||
> +	    *ep_state & EP_DROP_PENDING) {

Actually, what was the purpose of 'link_active' and 'connected' being
two separate flags? It seems everything treats them the same (modulo
negation), except here.

And here it doesn't matter either, right? You haven't added 'connected'
because EP_DROP_PENDING is the only one needed for correctness, and
'link_inactive' is merely an optimization to avoid queuing URBs which
will be thrown out later, preserved because it was already there.

Or at least that's what it seems, in absence of any explanation.

> +		xhci_dbg(xhci, "Can't queue urb, port disconnect or link inactive\n");
> +		ret = -ENODEV;
> +		goto free_priv;
> +	}
> +
>  	if (*ep_state & (EP_GETTING_STREAMS | EP_GETTING_NO_STREAMS)) {
>  		xhci_warn(xhci, "WARN: Can't enqueue URB, ep in streams transition state %x\n",
>  			  *ep_state);
> -- 
> 2.43.0
> 

  parent reply	other threads:[~2026-10-31  4:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-29 20:43 [PATCH v2] xhci: give back TDs and clean up ep0 after disconnect Mathias Nyman
2026-10-29 20:43 ` Mathias Nyman
2026-10-29 22:08   ` sashiko-bot
2026-10-30  5:22   ` Greg KH
2026-10-30 11:05     ` Mathias Nyman
2026-10-30 12:05       ` Michal Pecio
2026-10-30 16:57         ` Mathias Nyman
2026-10-30 19:27           ` Michal Pecio
2026-10-31  4:06   ` Michal Pecio [this message]
2026-10-29 22:11 ` 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=20261031050603.6067d2e5.michal.pecio@gmail.com \
    --to=michal.pecio@gmail.com \
    --cc=dennis@dsine.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mathias.nyman@linux.intel.com \
    --cc=regressions@lists.linux.dev \
    --cc=yiyu@yiyuzhou.io \
    /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.