From: Michael Grzeschik <mgr@pengutronix.de>
To: Dan Vacura <w36195@motorola.com>
Cc: Sergey Shtylyov <s.shtylyov@omp.ru>,
linux-usb@vger.kernel.org, balbi@kernel.org,
laurent.pinchart@ideasonboard.com, paul.elder@ideasonboard.com,
kernel@pengutronix.de, nicolas@ndufresne.ca,
kieran.bingham@ideasonboard.com
Subject: Re: [PATCH 1/5] usb: gadget: uvc: reset bytesused on queue cancel
Date: Wed, 6 Apr 2022 10:26:12 +0200 [thread overview]
Message-ID: <20220406082612.GC6952@pengutronix.de> (raw)
In-Reply-To: <YkxZzvbazHEX2EAg@p1g3>
[-- Attachment #1: Type: text/plain, Size: 1458 bytes --]
Hi Dan,
On Tue, Apr 05, 2022 at 10:01:34AM -0500, Dan Vacura wrote:
>Looks like we found the same issue, I submitted the same change the
>other week here:
>https://lore.kernel.org/all/20220331184024.23918-1-w36195@motorola.com/
>
>One difference is you had the reset outside of the queue lock. I figured
>to keep it within the lock since we can get a cancel while the pump
>worker is running and this can negate the reset. Do you agree?
Yes! Your patch is to favour and mine can be dropped from this series.
Thanks,
Michael
>
>On Tue, Apr 05, 2022 at 11:43:16AM +0300, Sergey Shtylyov wrote:
>> Hello!
>>
>> On 4/3/22 2:39 AM, Michael Grzeschik wrote:
>>
>> > On uvcg_queue_cancel the buf_used counter has to be reset. Since the
>> > encode function uses the variable to decide if the encoded data has
>> > reached the end of frame. Intermediate calls of uvcg_queue_cancel can
>> > therefor lead to miscalculations in the encode functions, if buf_used
>>
>> Therefore?
>>
>> > was not properly reset.
>> >
>> > Signed-off-by: Michael Grzeschik <m.grzeschik@pengutronix.de>
>> [...]
>>
>> MBR, Sergey
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-04-06 11:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-02 23:39 [PATCH 0/5] usb: gadget: uvc: fixes and improvements Michael Grzeschik
2022-04-02 23:39 ` [PATCH 1/5] usb: gadget: uvc: reset bytesused on queue cancel Michael Grzeschik
2022-04-05 8:43 ` Sergey Shtylyov
2022-04-05 15:01 ` Dan Vacura
2022-04-06 8:26 ` Michael Grzeschik [this message]
2022-04-02 23:39 ` [PATCH 2/5] usb: gadget: uvc: calculate the number of request depending on framesize Michael Grzeschik
2022-04-19 20:46 ` Laurent Pinchart
2022-05-08 22:48 ` Michael Grzeschik
2022-04-02 23:39 ` [PATCH 3/5] usb: gadget: uvc: increase worker prio to WQ_HIGHPRI Michael Grzeschik
2022-04-19 20:46 ` Laurent Pinchart
2022-04-29 18:51 ` Dan Vacura
2022-04-29 20:01 ` Michael Grzeschik
2022-05-02 9:00 ` Michael Grzeschik
2022-05-06 21:49 ` Dan Vacura
2022-09-28 20:12 ` Laurent Pinchart
2022-04-02 23:39 ` [PATCH 4/5] usb: gadget: uvc: call uvc uvcg_warn on completed status instead of uvcg_info Michael Grzeschik
2022-04-19 20:47 ` Laurent Pinchart
2022-04-02 23:39 ` [PATCH 5/5] usb: gadget: uvc: stop the pump on more conditions Michael Grzeschik
2022-04-04 11:30 ` kernel test robot
2022-04-04 13:07 ` Michael Grzeschik
2022-04-19 14:21 ` Greg KH
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=20220406082612.GC6952@pengutronix.de \
--to=mgr@pengutronix.de \
--cc=balbi@kernel.org \
--cc=kernel@pengutronix.de \
--cc=kieran.bingham@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-usb@vger.kernel.org \
--cc=nicolas@ndufresne.ca \
--cc=paul.elder@ideasonboard.com \
--cc=s.shtylyov@omp.ru \
--cc=w36195@motorola.com \
/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;
as well as URLs for NNTP newsgroup(s).