From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: kieran.bingham@ideasonboard.com
Cc: linux-usb@vger.kernel.org, Felipe Balbi <balbi@kernel.org>,
Joel Pepper <joel.pepper@rwth-aachen.de>,
Andrzej Pietrasiewicz <andrzej.p@samsung.com>
Subject: [v2,8/8] usb: gadget: uvc: configfs: Prevent format changes after linking header
Date: Mon, 24 Sep 2018 19:03:55 +0300 [thread overview]
Message-ID: <1776447.QiIAox8VW4@avalon> (raw)
Hi Kieran,
On Monday, 24 September 2018 15:50:45 EEST Kieran Bingham wrote:
> On 01/08/18 22:55, Laurent Pinchart wrote:
> > From: Joel Pepper <joel.pepper@rwth-aachen.de>
> >
> > While checks are in place to avoid attributes and children of a format
> > being manipulated after the format is linked into the streaming header,
> > the linked flag was never actually set, invalidating the protections.
>
> That explains what's wrong, but not what we do about it. How about adding:
>
> "Update the flag as appropriate in the header link calls."
Sounds good to me, I'll update that.
> > Signed-off-by: Joel Pepper <joel.pepper@rwth-aachen.de>
>
> Missing and S-o-B from Laurent here? (I guess that will be added later?)
I haven't modified the patch, so haven't added my SoB to send it to the
mailing list. I'll add it before issuing the pull request.
> Otherwise,
>
> Reviewed-by: Kieran Bingham <kieran.bingham@ideasonboard.com>
>
> > ---
> >
> > drivers/usb/gadget/function/uvc_configfs.c | 3 +++
> > 1 file changed, 3 insertions(+)
> >
> > diff --git a/drivers/usb/gadget/function/uvc_configfs.c
> > b/drivers/usb/gadget/function/uvc_configfs.c index
> > b8763343dcae..799dc32c5bc7 100644
> > --- a/drivers/usb/gadget/function/uvc_configfs.c
> > +++ b/drivers/usb/gadget/function/uvc_configfs.c
> > @@ -928,6 +928,7 @@ static int uvcg_streaming_header_allow_link(struct
> > config_item *src,>
> > format_ptr->fmt = target_fmt;
> > list_add_tail(&format_ptr->entry, &src_hdr->formats);
> > ++src_hdr->num_fmt;
> >
> > + ++target_fmt->linked;
> >
> > out:
> > mutex_unlock(&opts->lock);
> >
> > @@ -965,6 +966,8 @@ static void uvcg_streaming_header_drop_link(struct
> > config_item *src,>
> > break;
> >
> > }
> >
> > + --target_fmt->linked;
> > +
> >
> > out:
> > mutex_unlock(&opts->lock);
> > mutex_unlock(su_mutex);
next reply other threads:[~2018-09-24 16:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-24 16:03 Laurent Pinchart [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-09-24 12:50 [v2,8/8] usb: gadget: uvc: configfs: Prevent format changes after linking header Kieran Bingham
2018-08-01 21:55 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=1776447.QiIAox8VW4@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=andrzej.p@samsung.com \
--cc=balbi@kernel.org \
--cc=joel.pepper@rwth-aachen.de \
--cc=kieran.bingham@ideasonboard.com \
--cc=linux-usb@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.