From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
To: hverkuil-cisco@xs4all.nl
Cc: linux-media@vger.kernel.org, Sakari Ailus <sakari.ailus@linux.intel.com>
Subject: Re: [PATCH 1/3] vb2: add buf_validate callback
Date: Wed, 12 Dec 2018 07:13:19 -0200 [thread overview]
Message-ID: <20181212071319.409ed29c@coco.lan> (raw)
In-Reply-To: <20181203124603.17932-1-hverkuil-cisco@xs4all.nl>
Em Mon, 3 Dec 2018 13:46:01 +0100
hverkuil-cisco@xs4all.nl escreveu:
> From: Hans Verkuil <hverkuil-cisco@xs4all.nl>
>
> Adding the request API uncovered a pre-existing problem with
> validating output buffers.
>
> The problem is that for output buffers the driver has to validate
> the 'field' field of struct v4l2_buffer. This is critical when
> encoding or deinterlacing interlaced video.
>
> Drivers always did this in the buf_prepare callback, but that is
> not called from VIDIOC_QBUF in two situations: when queueing a
> buffer to a request and if VIDIOC_PREPARE_BUF has been called
> earlier for that buffer.
Hmm.. if I got it right, it will only affect drivers
using request API, right?
IMO, the description of the callback should be a way more
verbose, containing a summary of the explanation here.
>
> As a result of this the 'field' value is not validated.
>
> This patch adds a new buf_validate callback to validate the
> output buffer at QBUF time.
>
> Note that PREPARE_BUF doesn't need to validate this: it just
> locks the buffer memory and doesn't need nor want to know about
> how this buffer is actually going to be used. It's the QBUF ioctl
> that determines this.
>
> This issue was found by v4l2-compliance since it failed to replace
> V4L2_FIELD_ANY by a proper field value when testing the vivid video
> output in combination with requests.
>
> There never was a test before for the PREPARE_BUF/QBUF case, so even
> though this bug has been present for quite some time, it was never
> noticed.
>
> Signed-off-by: Hans Verkuil <hverkuil-cisco@xs4all.nl>
> ---
> drivers/media/common/videobuf2/videobuf2-core.c | 12 +++++++++---
> include/media/videobuf2-core.h | 5 +++++
> 2 files changed, 14 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/media/common/videobuf2/videobuf2-core.c b/drivers/media/common/videobuf2/videobuf2-core.c
> index 0ca81d495bda..42eb7716f8a9 100644
> --- a/drivers/media/common/videobuf2/videobuf2-core.c
> +++ b/drivers/media/common/videobuf2/videobuf2-core.c
> @@ -499,9 +499,9 @@ static int __vb2_queue_free(struct vb2_queue *q, unsigned int buffers)
> pr_info(" buf_init: %u buf_cleanup: %u buf_prepare: %u buf_finish: %u\n",
> vb->cnt_buf_init, vb->cnt_buf_cleanup,
> vb->cnt_buf_prepare, vb->cnt_buf_finish);
> - pr_info(" buf_queue: %u buf_done: %u buf_request_complete: %u\n",
> - vb->cnt_buf_queue, vb->cnt_buf_done,
> - vb->cnt_buf_request_complete);
> + pr_info(" buf_validate: %u buf_queue: %u buf_done: %u buf_request_complete: %u\n",
> + vb->cnt_buf_validate, vb->cnt_buf_queue,
> + vb->cnt_buf_done, vb->cnt_buf_request_complete);
> pr_info(" alloc: %u put: %u prepare: %u finish: %u mmap: %u\n",
> vb->cnt_mem_alloc, vb->cnt_mem_put,
> vb->cnt_mem_prepare, vb->cnt_mem_finish,
> @@ -1506,6 +1506,12 @@ int vb2_core_qbuf(struct vb2_queue *q, unsigned int index, void *pb,
> return -EBUSY;
> }
>
> + ret = call_vb_qop(vb, buf_validate, vb);
> + if (ret) {
> + dprintk(1, "buffer validation failed\n");
> + return ret;
> + }
> +
> if (req) {
> int ret;
>
> diff --git a/include/media/videobuf2-core.h b/include/media/videobuf2-core.h
> index e86981d615ae..c9f0f3f4ef9a 100644
> --- a/include/media/videobuf2-core.h
> +++ b/include/media/videobuf2-core.h
> @@ -294,6 +294,7 @@ struct vb2_buffer {
> u32 cnt_mem_num_users;
> u32 cnt_mem_mmap;
>
> + u32 cnt_buf_validate;
> u32 cnt_buf_init;
> u32 cnt_buf_prepare;
> u32 cnt_buf_finish;
> @@ -340,6 +341,9 @@ struct vb2_buffer {
> * @wait_finish: reacquire all locks released in the previous callback;
> * required to continue operation after sleeping while
> * waiting for a new buffer to arrive.
> + * @buf_validate: called every time the buffer is queued from userspace;
> + * drivers can use this to validate userspace-provided
> + * information; optional.
> * @buf_init: called once after allocating a buffer (in MMAP case)
> * or after acquiring a new USERPTR buffer; drivers may
> * perform additional buffer-related initialization;
> @@ -407,6 +411,7 @@ struct vb2_ops {
> void (*wait_prepare)(struct vb2_queue *q);
> void (*wait_finish)(struct vb2_queue *q);
>
> + int (*buf_validate)(struct vb2_buffer *vb);
> int (*buf_init)(struct vb2_buffer *vb);
> int (*buf_prepare)(struct vb2_buffer *vb);
> void (*buf_finish)(struct vb2_buffer *vb);
Thanks,
Mauro
prev parent reply other threads:[~2018-12-12 9:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-03 12:46 [PATCH 1/3] vb2: add buf_validate callback hverkuil-cisco
2018-12-03 12:46 ` [PATCH 2/3] vim2m: " hverkuil-cisco
2018-12-03 12:46 ` [PATCH 3/3] vivid: " hverkuil-cisco
2018-12-12 9:13 ` Mauro Carvalho Chehab [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=20181212071319.409ed29c@coco.lan \
--to=mchehab+samsung@kernel.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@linux.intel.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;
as well as URLs for NNTP newsgroup(s).