From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Ricardo Ribalda <ribalda@chromium.org>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Guenter Roeck <linux@roeck-us.net>,
Tomasz Figa <tfiga@chromium.org>,
Alan Stern <stern@rowland.harvard.edu>,
Hans Verkuil <hverkuil-cisco@xs4all.nl>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
Sean Paul <seanpaul@chromium.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Sergey Senozhatsky <senozhatsky@chromium.org>
Subject: Re: [PATCH v6 3/4] media: uvcvideo: Avoid race condition during unregister
Date: Wed, 25 Sep 2024 22:20:56 +0300 [thread overview]
Message-ID: <20240925192056.GC30399@pendragon.ideasonboard.com> (raw)
In-Reply-To: <20240614-guenter-mini-v6-3-7b7fdc3b21b3@chromium.org>
Hi Ricardo,
Thank you for the patch.
I'd write "during status unregister" in the subject line.
On Fri, Jun 14, 2024 at 12:41:29PM +0000, Ricardo Ribalda wrote:
> The control events are handled asynchronously by the driver. Once the
> control event are handled, the urb is re-submitted.
>
> If we simply kill the urb, there is a chance that a control event is
> waiting to be processed, which will re-submit the urb after the device is
> disconnected.
>
> uvc_status_suspend() flushes the async controls and stops the urb in a
> correct manner.
"Fix this by calling uvc_status_suspend(), which flushes the async
controls and kills the URB in a race-free manner."
Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> Reviewed-by: Sergey Senozhatsky <senozhatsky@chromium.org>
> Signed-off-by: Ricardo Ribalda <ribalda@chromium.org>
> ---
> drivers/media/usb/uvc/uvc_status.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/media/usb/uvc/uvc_status.c b/drivers/media/usb/uvc/uvc_status.c
> index 375a95dd3011..8fd8250110e2 100644
> --- a/drivers/media/usb/uvc/uvc_status.c
> +++ b/drivers/media/usb/uvc/uvc_status.c
> @@ -294,7 +294,7 @@ int uvc_status_init(struct uvc_device *dev)
>
> void uvc_status_unregister(struct uvc_device *dev)
> {
> - usb_kill_urb(dev->int_urb);
> + uvc_status_suspend(dev);
> uvc_input_unregister(dev);
> }
>
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2024-09-25 19:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-14 12:41 [PATCH v6 0/4] uvcvideo: Attempt N to land UVC race conditions fixes Ricardo Ribalda
2024-06-14 12:41 ` [PATCH v6 1/4] media: uvcvideo: Stop stream during unregister Ricardo Ribalda
2024-06-16 23:54 ` Laurent Pinchart
2024-06-17 7:22 ` Ricardo Ribalda
2024-09-25 8:32 ` Hans Verkuil
2024-09-25 9:50 ` Hans Verkuil
2024-09-25 19:29 ` Laurent Pinchart
2024-09-26 7:36 ` Hans Verkuil
2024-06-14 12:41 ` [PATCH v6 2/4] media: uvcvideo: Refactor the status irq API Ricardo Ribalda
2024-09-25 19:15 ` Laurent Pinchart
2024-09-25 19:22 ` Laurent Pinchart
2024-09-26 5:33 ` Ricardo Ribalda
2024-06-14 12:41 ` [PATCH v6 3/4] media: uvcvideo: Avoid race condition during unregister Ricardo Ribalda
2024-09-25 19:20 ` Laurent Pinchart [this message]
2024-06-14 12:41 ` [PATCH v6 4/4] media: uvcvideo: Exit early if there is not int_urb Ricardo Ribalda
2024-09-25 19:27 ` Laurent Pinchart
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=20240925192056.GC30399@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mchehab@kernel.org \
--cc=ribalda@chromium.org \
--cc=sakari.ailus@linux.intel.com \
--cc=seanpaul@chromium.org \
--cc=senozhatsky@chromium.org \
--cc=stern@rowland.harvard.edu \
--cc=tfiga@chromium.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox