From: Hans de Goede <hansg@kernel.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Desnes Nunes <desnesn@redhat.com>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@kernel.org
Subject: Re: [PATCH v2] media: uvcvideo: avoid variable shadowing in uvc_ctrl_cleanup_fh
Date: Mon, 7 Jul 2025 15:01:33 +0200 [thread overview]
Message-ID: <5fb10c0d-eb85-40d1-97f2-9e36d4d1f62c@kernel.org> (raw)
In-Reply-To: <20250707125028.GB12247@pendragon.ideasonboard.com>
Hi,
On 7-Jul-25 14:50, Laurent Pinchart wrote:
> Hi Hans,
>
> On Mon, Jul 07, 2025 at 02:43:09PM +0200, Hans de Goede wrote:
>> On 1-Jul-25 19:25, Desnes Nunes wrote:
>>> This avoids a variable loop shadowing occurring between the local loop
>>> iterating through the uvc_entity's controls and the global one going
>>> through the pending async controls of the file handle
>>>
>>> Cc: stable@kernel.org
>>> Fixes: 10acb9101355 ("media: uvcvideo: Increase/decrease the PM counter per IOCTL")
>>> Signed-off-by: Desnes Nunes <desnesn@redhat.com>
>>
>> Thank you for the new version.
>>
>> I've pushed this to uvc/for-next now:
>>
>> https://gitlab.freedesktop.org/linux-media/users/uvc/-/commits/for-next/
>
> As mentioned during the review (see
> 20250701192928.GB16835@pendragon.ideasonboard.com), I still prefer local
> loop variables. Can we use that please ?
Ok, I'll drop this from for-next.
Desnes, can you prepare a v3 moving the toplevel declation
inside the other loop please ?
Regards,
Hans
>> Note I had to manually apply the patch because of it conflicting with:
>>
>> https://gitlab.freedesktop.org/linux-media/users/uvc/-/commit/2b1e8e9f7bb30204ddb42887c4e554c131f003c9
>>
>> So if you want this backported to stable you will need to send
>> the original version to stable your self.
>>
>> I plan to send a pull-request with the changes from for-next this Thursday.
>>
>>> ---
>>> drivers/media/usb/uvc/uvc_ctrl.c | 4 ++--
>>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/drivers/media/usb/uvc/uvc_ctrl.c b/drivers/media/usb/uvc/uvc_ctrl.c
>>> index 44b6513c5264..532615d8484b 100644
>>> --- a/drivers/media/usb/uvc/uvc_ctrl.c
>>> +++ b/drivers/media/usb/uvc/uvc_ctrl.c
>>> @@ -3260,7 +3260,7 @@ int uvc_ctrl_init_device(struct uvc_device *dev)
>>> void uvc_ctrl_cleanup_fh(struct uvc_fh *handle)
>>> {
>>> struct uvc_entity *entity;
>>> - int i;
>>> + unsigned int i;
>>>
>>> guard(mutex)(&handle->chain->ctrl_mutex);
>>>
>>> @@ -3268,7 +3268,7 @@ void uvc_ctrl_cleanup_fh(struct uvc_fh *handle)
>>> return;
>>>
>>> list_for_each_entry(entity, &handle->chain->dev->entities, list) {
>>> - for (unsigned int i = 0; i < entity->ncontrols; ++i) {
>>> + for (i = 0; i < entity->ncontrols; ++i) {
>>> if (entity->controls[i].handle != handle)
>>> continue;
>>> uvc_ctrl_set_handle(handle, &entity->controls[i], NULL);
>>
>
next prev parent reply other threads:[~2025-07-07 13:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-01 17:25 [PATCH v2] media: uvcvideo: avoid variable shadowing in uvc_ctrl_cleanup_fh Desnes Nunes
2025-07-01 19:05 ` Ricardo Ribalda
2025-07-07 12:43 ` Hans de Goede
2025-07-07 12:50 ` Laurent Pinchart
2025-07-07 13:01 ` Hans de Goede [this message]
2025-07-08 12:40 ` Desnes Nunes
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=5fb10c0d-eb85-40d1-97f2-9e36d4d1f62c@kernel.org \
--to=hansg@kernel.org \
--cc=desnesn@redhat.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=stable@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 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).