All of lore.kernel.org
 help / color / mirror / Atom feed
From: Faisal Hassan <faisal.hassan@oss.qualcomm.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Thinh Nguyen <Thinh.Nguyen@synopsys.com>,
	Felipe Balbi <balbi@ti.com>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] usb: dwc3: gadget: linearize SG requests that exceed the TRB cache
Date: Fri, 30 Oct 2026 16:00:10 +0530	[thread overview]
Message-ID: <abb9b242-be39-4368-bfca-98a69dc795d2@oss.qualcomm.com> (raw)
In-Reply-To: <2026102912-iguana-purposely-496d@gregkh>

On 29-10-2026 03:25 pm, Greg Kroah-Hartman wrote:
> On Thu, Oct 29, 2026 at 12:40:06AM +0530, Faisal Hassan wrote:
>> Hi all,
>>
>> A gentle ping on this v2 when you get a chance.
>>
>> It addresses the sashiko review comments on v1: a linearized request is
>> now unmapped before its bounce buffer is freed, and an allocation
>> failure or a short SG list is returned from usb_ep_queue() instead of
>> leaving the request stuck on pending_list.
>>
>> Please let me know if you have any comments, or if you'd like me to
>> change anything.
> 
> You seem to have missed the review comments on this patch:
> 	https://lore.kernel.org/r/sashiko-outbox-162302@kernel.org

Hi Greg,

Sorry for the noise, and thank you for pointing me to the review. I
had read it but should have replied on the list before pinging.

Both comments look pre-existing to me:

1) The unmap/re-map leak of a request that is mapped but gets no TRB
    dates back to cdb55b39fab8 and 4a71fcb8ac5f and affects all
    requests. v2 only unmaps a linearized request before freeing its
    bounce buffer.

2) The isoc error return after the request is on pending_list comes
    from 25abad6a0584. v2 does not change it, as the new failure paths
    return before the request is queued.

I can fix 1) in a separate patch or as a first patch in a v3 series,
whichever you and Thinh prefer. For 2), please let me know if you want
it handled here.

Thanks for your patience, and sorry again for the extra mail.

Faisal

      reply	other threads:[~2026-10-30 10:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-04  3:14 [PATCH] usb: dwc3: gadget: linearize SG requests that exceed the TRB cache Faisal Hassan
2026-10-06 17:22 ` [PATCH v2] " Faisal Hassan
2026-10-06 17:41   ` sashiko-bot
2026-10-28 19:10   ` Faisal Hassan
2026-10-29  6:20     ` Greg Kroah-Hartman
2026-10-29  9:55     ` Greg Kroah-Hartman
2026-10-30 10:30       ` Faisal Hassan [this message]

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=abb9b242-be39-4368-bfca-98a69dc795d2@oss.qualcomm.com \
    --to=faisal.hassan@oss.qualcomm.com \
    --cc=Thinh.Nguyen@synopsys.com \
    --cc=balbi@ti.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    /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.