From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Ricardo Ribalda <ribalda@chromium.org>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
syzbot <syzkaller@googlegroups.com>
Subject: Re: [PATCH v1 1/1] media: uvc: Handle cameras with invalid descriptors
Date: Tue, 3 Jan 2023 22:54:37 +0200 [thread overview]
Message-ID: <Y7SWDUuHyCQWeGXY@pendragon.ideasonboard.com> (raw)
In-Reply-To: <CANiDSCsguMfWEHTGy3yry12uOFL=qELQO6tYwu9L-ueLW+bZpw@mail.gmail.com>
On Tue, Jan 03, 2023 at 03:55:54PM +0100, Ricardo Ribalda wrote:
> Hi Laurent
>
> I think we have missed this patch.
Pushed to
https://git.kernel.org/pub/scm/linux/kernel/git/pinchartl/linux.git/log/?h=next/uvc,
I'll send a pull request next week when Mauro comes back from vacation.
> On Mon, 24 Oct 2022 at 20:19, Laurent Pinchart wrote:
> > On Wed, Sep 21, 2022 at 11:52:29PM +0200, Ricardo Ribalda wrote:
> > > On Wed, 21 Sept 2022 at 23:16, Laurent Pinchart wrote:
> > > > On Wed, Sep 21, 2022 at 09:51:44AM +0200, Ricardo Ribalda wrote:
> > > > > Do you mean something like this?
> > > > >
> > > > > diff --git a/drivers/media/usb/uvc/uvc_entity.c
> > > > > b/drivers/media/usb/uvc/uvc_entity.c
> > > > > index 7c4d2f93d351..66d1f5da4ec7 100644
> > > > > --- a/drivers/media/usb/uvc/uvc_entity.c
> > > > > +++ b/drivers/media/usb/uvc/uvc_entity.c
> > > > > @@ -37,7 +37,7 @@ static int uvc_mc_create_links(struct uvc_video_chain *chain,
> > > > > continue;
> > > > >
> > > > > remote = uvc_entity_by_id(chain->dev, entity->baSourceID[i]);
> > > > > - if (remote == NULL)
> > > > > + if (remote == NULL || remote->num_pads == 0)
> > > > > return -EINVAL;
> > > >
> > > > Yes.
> > > >
> > > > >
> > > > > source = (UVC_ENTITY_TYPE(remote) == UVC_TT_STREAMING)
> > > > > @@ -46,6 +46,9 @@ static int uvc_mc_create_links(struct uvc_video_chain *chain,
> > > > > if (source == NULL)
> > > > > continue;
> > > > >
> > > > > + if (source->num_pads != remote->num_pads)
> > > > > + return -EINVAL;
> > > > > +
> > > >
> > > > But this I would have dropped, as the media_entity num_pads is
> > > > initialized from uvc_entity num_pads and neither are changed after.
> > >
> > > Works for me. Shall I send a v2 or you can take it?
> >
> > I'm handling it locally, will be in the next pull request.
> >
> > > > > remote_pad = remote->num_pads - 1;
> > > > > ret = media_create_pad_link(source, remote_pad,
> > > > > sink, i, flags);
> > > > >
> > > > > regarding making a new patch, whatever is easier for you ;)
> > > > >
> > > > >
> > > > > On Wed, 21 Sept 2022 at 02:53, Laurent Pinchart wrote:
> > > > > >
> > > > > > Hi Ricardo,
> > > > > >
> > > > > > Thank you for the patch.
> > > > > >
> > > > > > On Tue, Sep 20, 2022 at 04:04:55PM +0200, Ricardo Ribalda wrote:
> > > > > > > If the source entity does not contain any pads, do not create a link.
> > > > > > >
> > > > > > > Reported-by: syzbot <syzkaller@googlegroups.com>
> > > > > > > Signed-off-by: Ricardo Ribalda <ribalda@chromium.org>
> > > > > > >
> > > > > > > diff --git a/drivers/media/usb/uvc/uvc_entity.c b/drivers/media/usb/uvc/uvc_entity.c
> > > > > > > index 7c4d2f93d351..1f730cb72e58 100644
> > > > > > > --- a/drivers/media/usb/uvc/uvc_entity.c
> > > > > > > +++ b/drivers/media/usb/uvc/uvc_entity.c
> > > > > > > @@ -43,7 +43,7 @@ static int uvc_mc_create_links(struct uvc_video_chain *chain,
> > > > > > > source = (UVC_ENTITY_TYPE(remote) == UVC_TT_STREAMING)
> > > > > > > ? (remote->vdev ? &remote->vdev->entity : NULL)
> > > > > > > : &remote->subdev.entity;
> > > > > > > - if (source == NULL)
> > > > > > > + if (source == NULL || source->num_pads == 0)
> > > > > >
> > > > > > source->num_pads and remote->num_pads should always be identical, but as
> > > > > > the next line uses remote->num_pads, wouldn't it be better to test that
> > > > > > variable ? If so, I'd move the test a file lines earlier, with the
> > > > > > remote == NULL test.
> > > > > >
> > > > > > What do you think ? If you agree I can make that change when applying,
> > > > > > there's no need for a new version. Otherwise I'll keep the patch as-is.
> > > > > >
> > > > > > > continue;
> > > > > > >
> > > > > > > remote_pad = remote->num_pads - 1;
--
Regards,
Laurent Pinchart
prev parent reply other threads:[~2023-01-03 20:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 14:04 [PATCH v1 0/1] [RESEND] uvc: Handle cames with invalid descriptors Ricardo Ribalda
2022-09-20 14:04 ` [PATCH v1 1/1] media: uvc: Handle cameras " Ricardo Ribalda
2022-09-21 0:53 ` Laurent Pinchart
2022-09-21 7:51 ` Ricardo Ribalda
2022-09-21 21:16 ` Laurent Pinchart
2022-09-21 21:52 ` Ricardo Ribalda
2022-10-24 18:18 ` Laurent Pinchart
2023-01-03 14:55 ` Ricardo Ribalda
2023-01-03 20:54 ` Laurent Pinchart [this message]
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=Y7SWDUuHyCQWeGXY@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=ribalda@chromium.org \
--cc=syzkaller@googlegroups.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