[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2025041508-rockslide-endpoint-a48b@gregkh>
Date: Tue, 15 Apr 2025 14:26:26 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Michal Pecio <michal.pecio@...il.com>
Cc: Mathias Nyman <mathias.nyman@...el.com>,
Minas Harutyunyan <hminas@...opsys.com>,
Linus Walleij <linus.walleij@...aro.org>,
Alan Stern <stern@...land.harvard.edu>, linux-usb@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] usb: hcd: Add a usb_device argument to
hc_driver.endpoint_reset()
On Tue, Apr 15, 2025 at 11:10:03AM +0200, Michal Pecio wrote:
> xHCI needs usb_device here, so it stored it in host_endpoint.hcpriv,
> which proved problematic due to some unexpected call sequences from
> USB core, and generally made the code more complex than it has to be.
>
> Make USB core supply it directly and simplify xhci_endpoint_reset().
> Use the xhci_check_args() helper for preventing resets of emulated
> root hub endpoints and for argument validation.
>
> Update other drivers which also define such callback to accept the
> new argument and ignore it, as it seems to be of no use for them.
>
> This fixes a 6.15-rc1 regression reported by Paul, which I was able
> to reproduce, where xhci_hcd doesn't handle endpoint_reset() after
> endpoint_disable() not followed by add_endpoint(). If a configured
> device is reset, stalling endpoints start to get stuck permanently.
As this fixes a bug, can you add a Fixes: tag with the needed
information?
thanks,
greg k-h
Powered by blists - more mailing lists