From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Pawel Osciak <pawel@osciak.com>
Cc: linux-media@vger.kernel.org,
Marek Szyprowski <m.szyprowski@samsung.com>,
Kyungmin Park <kyungmin.park@samsung.com>,
Hans Verkuil <hverkuil@xs4all.nl>
Subject: Re: [PATCH v2] videobuf2-core: Verify planes lengths for output buffers
Date: Mon, 12 Nov 2012 12:35:35 +0100 [thread overview]
Message-ID: <1628324.o2sLjPETOy@avalon> (raw)
In-Reply-To: <CAMm-=zCd3T=YnkjxTPej_2J-MaiCtsrH5entkiz5GgKCBg31rw@mail.gmail.com>
Hi Pawel,
On Friday 09 November 2012 15:33:22 Pawel Osciak wrote:
> On Tue, Oct 16, 2012 at 8:37 AM, Laurent Pinchart wrote:
> > For output buffers application provide to the kernel the number of bytes
> > they stored in each plane of the buffer. Verify that the value is
> > smaller than or equal to the plane length.
> >
> > Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> > Acked-by: Hans Verkuil <hans.verkuil@cisco.com>
> > ---
>
> Acked-by: Pawel Osciak <pawel@osciak.com>
You're listed, as well as Marek and Kyungmin, as videobuf2 maintainers. When
you ack a videobuf2 patch, should we assume that you will take it in your git
tree ?
> > drivers/media/v4l2-core/videobuf2-core.c | 39 +++++++++++++++++++++++++
> > 1 files changed, 39 insertions(+), 0 deletions(-)
> >
> > Changes compared to v1:
> >
> > - Sanity check the data_offset value for each plane.
> >
> > diff --git a/drivers/media/v4l2-core/videobuf2-core.c
> > b/drivers/media/v4l2-core/videobuf2-core.c index 432df11..479337d 100644
> > --- a/drivers/media/v4l2-core/videobuf2-core.c
> > +++ b/drivers/media/v4l2-core/videobuf2-core.c
> > @@ -296,6 +296,41 @@ static int __verify_planes_array(struct vb2_buffer
> > *vb, const struct v4l2_buffer>
> > }
> >
> > /**
> >
> > + * __verify_length() - Verify that the bytesused value for each plane
> > fits in + * the plane length and that the data offset doesn't exceed the
> > bytesused value. + */
> > +static int __verify_length(struct vb2_buffer *vb, const struct
> > v4l2_buffer *b) +{
> > + unsigned int length;
> > + unsigned int plane;
> > +
> > + if (!V4L2_TYPE_IS_OUTPUT(b->type))
> > + return 0;
> > +
> > + if (V4L2_TYPE_IS_MULTIPLANAR(b->type)) {
> > + for (plane = 0; plane < vb->num_planes; ++plane) {
> > + length = (b->memory == V4L2_MEMORY_USERPTR)
> > + ? b->m.planes[plane].length
> > + : vb->v4l2_planes[plane].length;
> > +
> > + if (b->m.planes[plane].bytesused > length)
> > + return -EINVAL;
> > + if (b->m.planes[plane].data_offset >=
> > + b->m.planes[plane].bytesused)
> > + return -EINVAL;
> > + }
> > + } else {
> > + length = (b->memory == V4L2_MEMORY_USERPTR)
> > + ? b->length : vb->v4l2_planes[0].length;
> > +
> > + if (b->bytesused > length)
> > + return -EINVAL;
> > + }
> > +
> > + return 0;
> > +}
> > +
> > +/**
> > * __buffer_in_use() - return true if the buffer is in use and
> > * the queue cannot be freed (by the means of REQBUFS(0)) call
> > */
> > @@ -975,6 +1010,10 @@ static int __buf_prepare(struct vb2_buffer *vb,
> > const struct v4l2_buffer *b)>
> > struct vb2_queue *q = vb->vb2_queue;
> > int ret;
> >
> > + ret = __verify_length(vb, b);
> > + if (ret < 0)
> > + return ret;
> > +
> > switch (q->memory) {
> > case V4L2_MEMORY_MMAP:
> > ret = __qbuf_mmap(vb, b);
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2012-11-12 11:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-16 15:37 [PATCH v2] videobuf2-core: Verify planes lengths for output buffers Laurent Pinchart
2012-11-09 23:33 ` Pawel Osciak
2012-11-12 11:35 ` Laurent Pinchart [this message]
2013-08-07 10:44 ` Laurent Pinchart
2013-08-08 12:14 ` Marek Szyprowski
2013-08-08 12:35 ` Laurent Pinchart
2013-08-26 13:55 ` Sylwester Nawrocki
2013-08-26 14:32 ` Mauro Carvalho Chehab
2013-08-26 14:41 ` Laurent Pinchart
2013-08-26 15:03 ` Sylwester Nawrocki
2013-08-27 8:50 ` 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=1628324.o2sLjPETOy@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=hverkuil@xs4all.nl \
--cc=kyungmin.park@samsung.com \
--cc=linux-media@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=pawel@osciak.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