From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Hangyu Hua <hbh25y@gmail.com>
Cc: mchehab@kernel.org, linux-media@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] media: uvc_video: fix bit overflow in uvc_probe_video
Date: Thu, 24 Mar 2022 15:52:21 +0200 [thread overview]
Message-ID: <Yjx3laKM9Ah+1PRC@pendragon.ideasonboard.com> (raw)
In-Reply-To: <20220324091308.44799-1-hbh25y@gmail.com>
Hi Hangyu,
Thank you for the patch.
On Thu, Mar 24, 2022 at 05:13:08PM +0800, Hangyu Hua wrote:
> probe->dwMaxPayloadTransferSize is a 32bit value, but bandwidth is 16bit. This
> may lead to a bit overflow.
>
> Signed-off-by: Hangyu Hua <hbh25y@gmail.com>
> ---
> drivers/media/usb/uvc/uvc_video.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/media/usb/uvc/uvc_video.c b/drivers/media/usb/uvc/uvc_video.c
> index 1b4cc934109e..cc4878373aa7 100644
> --- a/drivers/media/usb/uvc/uvc_video.c
> +++ b/drivers/media/usb/uvc/uvc_video.c
> @@ -383,7 +383,7 @@ int uvc_probe_video(struct uvc_streaming *stream,
> struct uvc_streaming_control *probe)
> {
> struct uvc_streaming_control probe_min, probe_max;
> - u16 bandwidth;
> + u32 bandwidth;
> unsigned int i;
> int ret;
>
> @@ -422,7 +422,7 @@ int uvc_probe_video(struct uvc_streaming *stream,
> break;
>
> bandwidth = probe->dwMaxPayloadTransferSize;
> - if (bandwidth <= stream->maxpsize)
> + if (bandwidth <= (u32)stream->maxpsize)
The cast to u32 isn't needed, it's implicit.
This could actually be written
if (probe->dwMaxPayloadTransferSize <= stream->maxpsize)
The bandwidth local variable can be dropped. Could you submit a v2 with
this change ?
> break;
>
> if (stream->dev->quirks & UVC_QUIRK_PROBE_MINMAX) {
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2022-03-24 13:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-24 9:13 Hangyu Hua
2022-03-24 13:52 ` Laurent Pinchart [this message]
2022-03-25 1:35 ` Hangyu Hua
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=Yjx3laKM9Ah+1PRC@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=hbh25y@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@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
all inboxes | Powered by JetHome®