Re: [PATCH v3] usb: dwc3: gadget: Prevent EP resource conflicts during StartTransfer

[Thinh Nguyen <Thinh.Nguyen@synopsys.com>]

On Thu, Sep 24, 2026, Selvarasu Ganesan wrote:
> 
> On 3/7/2026 3:11 AM, Thinh Nguyen wrote:
> > On Fri, Mar 06, 2026, Selvarasu Ganesan wrote:
> >> On 3/3/2026 6:09 AM, Thinh Nguyen wrote:
> >>> On Sat, Feb 28, 2026, Thinh Nguyen wrote:
> >>>> On Fri, Feb 27, 2026, Selvarasu Ganesan wrote:
> >>>>> The below “No resource for ep” warning appears when a StartTransfer
> >>>>> command is issued for bulk or interrupt endpoints in
> >>>>> `dwc3_gadget_ep_enable` while a previous StartTransfer on the same
> >>>>> endpoint is still in progress. The gadget functions drivers can invoke
> >>>>> `usb_ep_enable` (which triggers a new StartTransfer command) before the
> >>>>> earlier transfer has completed. Because the previous StartTransfer is
> >>>>> still active, `dwc3_gadget_ep_disable` can skip the required
> >>>>> `EndTransfer` due to `DWC3_EP_DELAY_STOP`, leading to the endpoint
> >>>>> resources are busy for previous StartTransfer and warning ("No resource
> >>>>> for ep") from dwc3 driver.
> >>>>>
> >>>>> Additionally, a race condition exists between dwc3_gadget_ep_disable()
> >>>>> and dwc3_gadget_ep_queue() when manipulating dep->flags. When
> >>>>> dwc3_gadget_ep_disable() calls dwc3_gadget_giveback(), the dwc->lock is
> >>>>> temporarily released. If dwc3_gadget_ep_queue() runs in that window, it
> >>>>> may set the DWC3_EP_TRANSFER_STARTED flag as part of
> >>>>> dwc3_send_gadget_ep_cmd(). When ep_disable resumes, it unconditionally
> >>>>> clears all flags except those explicitly masked, potentially clearing
> >>>>> DWC3_EP_TRANSFER_STARTED even though a new transfer has started. This
> >>>>> leads to "No resource for ep" warnings on subsequent StartTransfer
> >>>>> attempts.
> >>>>>
> >>>>> The underlying framework issue is that usb_ep_disable() is expected to
> >>>>> complete pending requests before returning, but is allowed to be called
> >>>>> from interrupt context where sleeping to wait for completion is not
> >>>>> possible.
> >>>>>
> >>>>> As temporary workarounds for this framework limitation:
> >>>>>
> >>>>> 1. In __dwc3_gadget_ep_enable(), add a check for the
> >>>>>      DWC3_EP_TRANSFER_STARTED flag before issuing a new StartTransfer.
> >>>>>      This prevents a second StartTransfer on an already busy endpoint,
> >>>>>      eliminating the resource conflict.
> >>>>>
> >>>>> 2. In __dwc3_gadget_ep_disable(), preserve the DWC3_EP_TRANSFER_STARTED
> >>>>>      flag when masking dep->flags if it is actually set, preventing the
> >>>>>      race with dwc3_gadget_ep_queue() from corrupting the flag state.
> >>>>>
> >>>>> These changes eliminate the "No resource for ep" warnings and potential
> >>>>> kernel panics caused by panic_on_warn.
> >>>>>
> >>>>> dwc3 13200000.dwc3: No resource for ep1out
> >>>>> WARNING: CPU: 0 PID: 700 at drivers/usb/dwc3/gadget.c:398 dwc3_send_gadget_ep_cmd+0x2f8/0x76c
> >>>>> Call trace:
> >>>>> dwc3_send_gadget_ep_cmd+0x2f8/0x76c
> >>>>> __dwc3_gadget_ep_enable+0x490/0x7c0
> >>>>> dwc3_gadget_ep_enable+0x6c/0xe4
> >>>>> usb_ep_enable+0x5c/0x15c
> >>>>> mp_eth_stop+0xd4/0x11c
> >>>>> __dev_close_many+0x160/0x1c8
> >>>>> __dev_change_flags+0xfc/0x220
> >>>>> dev_change_flags+0x24/0x70
> >>>>> devinet_ioctl+0x434/0x524
> >>>>> inet_ioctl+0xa8/0x224
> >>>>> sock_do_ioctl+0x74/0x128
> >>>>> sock_ioctl+0x3bc/0x468
> >>>>> __arm64_sys_ioctl+0xa8/0xe4
> >>>>> invoke_syscall+0x58/0x10c
> >>>>> el0_svc_common+0xa8/0xdc
> >>>>> do_el0_svc+0x1c/0x28
> >>>>> el0_svc+0x38/0x88
> >>>>> el0t_64_sync_handler+0x70/0xbc
> >>>>> el0t_64_sync+0x1a8/0x1ac
> >>>>>
> >>>>> Cc: stable@vger.kernel.org
> >>>>> Signed-off-by: Selvarasu Ganesan <selvarasu.g@samsung.com>
> >>>>> ---
> >>>>>
> >>>>> Note: No Fixes tag is added because this is a workaround for the
> >>>>> gadget framework issue where the gadget framework calls usb_ep_disable()
> >>>>> in interrupt context without ensuring endpoint flushing completes.
> >>>>> A proper fix requires refactoring the framework to make sure
> >>>>> usb_ep_disable is invoked in process context.
> >>>>>
> >>>>> Changes in v3:
> >>>>>    - Revised the commit message to detail the real gadget framework issue
> >>>>>      pointed out by the reviewer.
> >>>>>    - Merged the two fixes for the same ep wringing into one patch.
> >>>>> Link to v2: https://urldefense.com/v3/__https://protect2.fireeye.com/v1/url?k=5535d0f4-344e7a7d-55345bbb-74fe48600034-c617d7b77912682d&q=1&e=2a6508e6-6363-4d6e-b6ab-ce6c77832c8d&u=https*3A*2F*2Flore.kernel.org*2Flinux-usb*2F20251117155920.643-1-selvarasu.g*40samsung.com*2F__;JSUlJSUlJQ!!A4F2R9G_pg!dR0yufG2VvgMnkC0ZJ4eK3I5v7C5q2ry8MYAYSNdWhMNM2zPkO35fGBJJHPS-GhG4y9hzmrCcO16V1ASehHBYxvxQWQ$ 
> >>>>>
> >>>>> Changes in v2:
> >>>>> - Removed change-id.
> >>>>> - Updated commit message.
> >>>>> Link to v1: https://urldefense.com/v3/__https://protect2.fireeye.com/v1/url?k=c8daed0d-a9a14784-c8db6642-74fe48600034-8488506d5854e40d&q=1&e=2a6508e6-6363-4d6e-b6ab-ce6c77832c8d&u=https*3A*2F*2Flore.kernel.org*2Flinux-usb*2F20251117152812.622-1-selvarasu.g*40samsung.com*2F__;JSUlJSUlJQ!!A4F2R9G_pg!dR0yufG2VvgMnkC0ZJ4eK3I5v7C5q2ry8MYAYSNdWhMNM2zPkO35fGBJJHPS-GhG4y9hzmrCcO16V1ASehHB1Y4qk_k$ 
> >>>>> ---
> >>>>>    drivers/usb/dwc3/gadget.c | 22 ++++++++++++++++++++--
> >>>>>    1 file changed, 20 insertions(+), 2 deletions(-)
> >>>>>
> >>>>> diff --git a/drivers/usb/dwc3/gadget.c b/drivers/usb/dwc3/gadget.c
> >>>>> index 0a688904ce8c5..3af1bbfe3d92b 100644
> >>>>> --- a/drivers/usb/dwc3/gadget.c
> >>>>> +++ b/drivers/usb/dwc3/gadget.c
> >>>>> @@ -971,8 +971,9 @@ static int __dwc3_gadget_ep_enable(struct dwc3_ep *dep, unsigned int action)
> >>>>>    	 * Issue StartTransfer here with no-op TRB so we can always rely on No
> >>>>>    	 * Response Update Transfer command.
> >>>>>    	 */
> >>>>> -	if (usb_endpoint_xfer_bulk(desc) ||
> >>>>> -			usb_endpoint_xfer_int(desc)) {
> >>>>> +	if ((usb_endpoint_xfer_bulk(desc) ||
> >>>>> +			usb_endpoint_xfer_int(desc)) &&
> >>>>> +			!(dep->flags & DWC3_EP_TRANSFER_STARTED)) {
> >>>>>    		struct dwc3_gadget_ep_cmd_params params;
> >>>>>    		struct dwc3_trb	*trb;
> >>>>>    		dma_addr_t trb_dma;
> >>>>> @@ -1096,6 +1097,23 @@ static int __dwc3_gadget_ep_disable(struct dwc3_ep *dep)
> >>>>>    	 */
> >>>>>    	if (dep->flags & DWC3_EP_DELAY_STOP)
> >>>>>    		mask |= (DWC3_EP_DELAY_STOP | DWC3_EP_TRANSFER_STARTED);
> >>>>> +
> >>>>> +	/*
> >>>>> +	 * When dwc3_gadget_ep_disable() calls dwc3_gadget_giveback(),
> >>>>> +	 * the dwc->lock is temporarily released. If dwc3_gadget_ep_queue()
> >>>>> +	 * runs in that window it may set the DWC3_EP_TRANSFER_STARTED flag as
> >>>>> +	 * part of dwc3_send_gadget_ep_cmd. The original code cleared the flag
> >>>>> +	 * unconditionally in the mask operation, which could overwrite the
> >>>>> +	 * concurrent modification.
> >>>>> +	 *
> >>>>> +	 * As a workaround for the interrupt context constraint where we cannot
> >>>>> +	 * wait for endpoint flushing, preserve the DWC3_EP_TRANSFER_STARTED
> >>>>> +	 * flag if it is set, avoiding resource conflicts until the framework
> >>>>> +	 * is fixed to properly synchronize endpoint lifecycle management.
> >>>>> +	 */
> >>>>> +	if (dep->flags & DWC3_EP_TRANSFER_STARTED)
> >>>>> +		mask |= DWC3_EP_TRANSFER_STARTED;
> >>>>> +
> >>>>>    	dep->flags &= mask;
> >>>>>    
> >>>>>    	/* Clear out the ep descriptors for non-ep0 */
> >>>>> -- 
> >>>>> 2.34.1
> >>>>>
> >>>> Acked-by: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
> >>>>
> >>> Oh wait, don't pick this patch up yet.
> >>>
> >>> This will cause a regression for UAS device. When switching alt-setting
> >>> interface for BOT to UASP, the device needs to issue a Start Transfer
> >>> command.
> >>>
> >>> This workaround won't work. Can we fix the usb_ep_disable() interface
> >>> and rework this instead?
> >>>
> >>> BR,
> >>> Thinh
> >> Hi Thinh,
> >>
> >> We’re trying to see how this change could cause a regression for UAS
> >> devices.
> >> Could you explain why the workaround might be a problem for UAS? Are you
> >> concerned that it could miss a valid StartTransfer when a previous
> >> transfer finishes later than expected as part of ep_disable?
> > In UAS, the device controller uses the first PRIME to synchronize with
> > the host to determine whether the Start Transfer command can initiate
> > the stream. After configuring an endpoint, if we issue the StartTransfer
> > command too late, then the device controller may not initiate the
> > transfer (sending ERDY), and host will not know when to start the
> > transfer.
> 
> 
> HI Thinh,
> 
> Sorry for the delayed response. We're seeing this issue a lot in Exynos 
> platform, so we want to get it fixed.
> 
> Thanks for the explanation about UASP in last comment.
> 
> We agree that for UASP, the new StartTransfer sent in ep_enable() is 
> what makes the controller send ERDY for the host's first PRIME. The old 
> patch skipped that StartTransfer that was wrong. If it is skipped and no 
> request is queued right away, the controller never sends ERDY for the 
> first PRIME and the UAS device possible hangs as you mentioned.
> 
> The new patch is simpler, we won't skip it and just trigger it once the 
> inflight end transfer is done.
> 
> Please see the proposed sequence,
> 
>    1. usb_ep_disable() --> EndTransfer deferred due to pending control 
> transfer data/status stages (DWC3_EP_DELAY_STOP), old transfer still 
> active in HW.
>    2. usb_ep_enable() on the same endpoint --> instead of issuing the 
> new StartTransfer, set DWC3_EP_PENDING_START_TRANSFER (New flag) as below,
> 
>    /* __dwc3_gadget_ep_enable() */
>    if (dep->flags & (DWC3_EP_DELAY_STOP |
>                      DWC3_EP_END_TRANSFER_PENDING |
>                      DWC3_EP_TRANSFER_STARTED))
>        dep->flags |= DWC3_EP_PENDING_START_TRANSFER;
>    else
>        ret = dwc3_gadget_ep_start_noop_transfer(dep);   /* unchanged path */
> 
>    3. Control request finishes --> next SETUP --> existing delayed stop 
> retry in dwc3_ep0_out_start() sends the EndTransfer for all delayed stop 
> endpoints.
>    4. EndTransfer completion and trigger a previously skipped 
> StartTransfer in ep_enable by checking DWC3_EP_PENDING_START_TRANSFER.
> 
>    /* dwc3_gadget_endpoint_command_complete() */
>    if (dep->flags & DWC3_EP_PENDING_START_TRANSFER) {
>        dep->flags &= ~DWC3_EP_PENDING_START_TRANSFER;
>        dwc3_gadget_ep_start_noop_transfer(dep);
>    }
> 
> So the endpoint gets the same start/stop sequence you described, only 
> sent later, it goes out as soon as the EndTransfer finishes. So this is 
> high possible of happens before the host's first PRIME arrives. ERDY is 
> still sent, no UAS regression.
> 
> The below testing log is for the reference. You can see the timestamp 
> where pending start transfer triggered.
> 
> [ 3273.597476]  Entry __dwc3_gadget_ep_disable
> [ 3273.597481]  dwc3_remove_requests ep1out skip stop transfer due to 
> DWC3_EP_DELAY_STOP
> [ 3273.597510]  Entry __dwc3_gadget_ep_enable 1045 dep->name =ep1out 
> dep->flags =e009
> [ 3273.597590]  dwc3_gadget_endpoint_command_complete 3857 dep->name 
> =ep1out dep->flags =4009 --> Triggered skipped Start transfer when 
> endpoint command completion is done.
> 

Hi Selvarasu,

I just wanted to point out that dwc3_gadget_ep_start_noop_transfer()
should only be needed for stream endpoints. I'll take a closer look at
the rest of the changes later this week.

Regarding the original comment about avoiding the wait for command
completion due to the No Response Update Transfer command does not
provide any meaningful performance benefit since it only applies to the
initial Start Transfer command.

Thanks,
Thinh