public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Michael Grzeschik <m.grzeschik@pengutronix.de>
Cc: linux-usb@vger.kernel.org, linux-media@vger.kernel.org,
	balbi@kernel.org, kernel@pengutronix.de,
	Daniel Scally <dan.scally@ideasonboard.com>,
	Kieran Bingham <kieran.bingham@ideasonboard.com>
Subject: Re: [PATCH v2] usb: gadget: uvc: don't put item still in use
Date: Fri, 30 Sep 2022 19:17:38 +0300	[thread overview]
Message-ID: <YzcWompDLd7iIip+@pendragon.ideasonboard.com> (raw)
In-Reply-To: <20220930122839.1747279-1-m.grzeschik@pengutronix.de>

Hi Michael,

(Cc'ing Kieran and Dan)

Thank you for the patch.

On Fri, Sep 30, 2022 at 02:28:39PM +0200, Michael Grzeschik wrote:
> With the patch "588b9e85609b (usb: gadget: uvc: add v4l2 enumeration api
> calls)" the driver is keeping a list of configfs entries currently
> configured. The list is used in uvc_v4l2 on runtime.

s/on runtime/at runtime/

> The driver now is giving back the list item just after it was referenced
> with config_item_put. It also calls config_item_put on uvc_free, which
> is the only and right place to give back the reference. This patch fixes
> the issue by removing the extra config_item_put in uvc_alloc.
> 
> Fixes: 588b9e85609b (usb: gadget: uvc: add v4l2 enumeration api calls)

I still don't like this much :-( As shown by this fix, the additional
complexity that it incurs on the kernel side can cause bugs, and the
gain for userspace is quite minimal in my opinion, as parsing configfs
(or obtaining that information out-of-band through other means) will
still be needed anyway to handle controls properly (I think we have
agreed that userspace needs to handle the UVC requests in any case).

> Signed-off-by: Michael Grzeschik <m.grzeschik@pengutronix.de>
> ---
> v1 -> v2: - fixed commitish to valid one from usb-next tree
> 
>  drivers/usb/gadget/function/f_uvc.c | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/drivers/usb/gadget/function/f_uvc.c b/drivers/usb/gadget/function/f_uvc.c
> index e6948cf8def30b..8bc591431d153e 100644
> --- a/drivers/usb/gadget/function/f_uvc.c
> +++ b/drivers/usb/gadget/function/f_uvc.c
> @@ -995,7 +995,6 @@ static struct usb_function *uvc_alloc(struct usb_function_instance *fi)
>  		goto err_config;
>  
>  	uvc->header = to_uvcg_streaming_header(h);
> -	config_item_put(h);

Assuming we want to keep 588b9e85609b, the fix seems right.

>  	if (!uvc->header->linked) {
>  		mutex_unlock(&opts->lock);
>  		kfree(uvc);

-- 
Regards,

Laurent Pinchart

  reply	other threads:[~2022-09-30 16:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-29 14:41 [PATCH] usb: gadget: uvc: don't put item still in use Michael Grzeschik
2022-09-30 11:58 ` Greg KH
2022-09-30 12:28   ` [PATCH v2] " Michael Grzeschik
2022-09-30 16:17     ` Laurent Pinchart [this message]
2022-09-30 20:44       ` Michael Grzeschik
2022-10-02 22:49         ` Michael Grzeschik

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=YzcWompDLd7iIip+@pendragon.ideasonboard.com \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=balbi@kernel.org \
    --cc=dan.scally@ideasonboard.com \
    --cc=kernel@pengutronix.de \
    --cc=kieran.bingham@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=m.grzeschik@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