Linux USB
 help / color / mirror / Atom feed
From: Avichal Rakesh <arakesh@google.com>
To: Michael Grzeschik <mgr@pengutronix.de>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Daniel Scally <dan.scally@ideasonboard.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 0/2] usb: gadget: uvc: stability fixes when stopping streams
Date: Wed, 27 Sep 2023 13:47:38 -0700	[thread overview]
Message-ID: <1b8bb18d-460e-48cd-ab7d-80af8910423b@google.com> (raw)
In-Reply-To: <bb962593-9665-4bb1-be14-c56ce17b9073@google.com>



On 9/19/23 11:24, Avichal Rakesh wrote:
> 
> 
> On 9/15/23 18:35, Avichal Rakesh wrote:
>>
>>
>> On 9/15/23 16:16, Michael Grzeschik wrote:
>>> Hi Avichal
>>>
>>> On Thu, Sep 14, 2023 at 04:05:36PM -0700, Avichal Rakesh wrote:
>>>> On Mon, Sep 11, 2023 at 9:19 PM Avichal Rakesh <arakesh@google.com> wrote:
>>>>>
>>>>> We have been seeing two main bugs when stopping stream:
>>>>> 1. attempting to queue usb_requests on a disabled usb endpoint, and
>>>>> 2. use-after-free problems for inflight requests
>>>>>

>>>
>>> The error path triggering these list errors are usually in the
>>> dwc3 driver handling the cancelled or completed list.
>>
>> It looks like we're still freeing un-returned requests :(. If you still have
>> the setup can you pull the uvc logs to see if waiting for requests to be returned timed 
>> out? I wonder if dwc3's interrupt handler is being scheduled too late. 500ms seemed
>> like a reasonable time out to me, but this seems to prove otherwise.
>>
> 
> 
> Hey Michael, were you able to look into the comments from the previous
> email? 
> 

Bumping the thread up. Laurent, Dan, and Michael: the patches are ready to
review/test. Please take a look when possible. 

Thank you!
Avi.

      reply	other threads:[~2023-09-27 20:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-12  4:19 [PATCH v1 0/2] usb: gadget: uvc: stability fixes when stopping streams Avichal Rakesh
2023-09-12  4:19 ` [PATCH v1 1/2] usb: gadget: uvc: prevent use of disabled endpoint Avichal Rakesh
2023-09-12  4:19 ` [PATCH v1 2/2] usb: gadget: uvc: prevent de-allocating inflight usb_requests Avichal Rakesh
2023-09-20 20:03   ` [PATCH v2 " Avichal Rakesh
2023-09-28 20:19     ` [PATCH v3 " Avichal Rakesh
2023-09-28 21:04       ` Michael Grzeschik
2023-09-30 19:16         ` Avichal Rakesh
2023-09-14 23:05 ` [PATCH v1 0/2] usb: gadget: uvc: stability fixes when stopping streams Avichal Rakesh
2023-09-15 23:16   ` Michael Grzeschik
2023-09-16  1:35     ` Avichal Rakesh
2023-09-19 18:24       ` Avichal Rakesh
2023-09-27 20:47         ` Avichal Rakesh [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=1b8bb18d-460e-48cd-ab7d-80af8910423b@google.com \
    --to=arakesh@google.com \
    --cc=dan.scally@ideasonboard.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mgr@pengutronix.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox