From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: linux-media@vger.kernel.org, hverkuil@xs4all.nl, mchehab@kernel.org
Subject: Re: [PATCH 1/3] videobuf2-core: Prevent size alignment wrapping buffer size to 0
Date: Thu, 13 Dec 2018 14:49:44 +0200 [thread overview]
Message-ID: <11116293.zm9aLRIdQE@avalon> (raw)
In-Reply-To: <20181213104006.401-2-sakari.ailus@linux.intel.com>
Hi Sakari,
Thank you for the patch.
On Thursday, 13 December 2018 12:40:04 EET Sakari Ailus wrote:
> PAGE_ALIGN() may wrap the buffer size around to 0. Prevent this by
> checking that the aligned value is not smaller than the unaligned one.
>
> Note on backporting to stable: the file used to be under
> drivers/media/v4l2-core, it was moved to the current location after 4.14.
>
> Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
> Cc: stable@vger.kernel.org
> ---
> drivers/media/common/videobuf2/videobuf2-core.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/media/common/videobuf2/videobuf2-core.c
> b/drivers/media/common/videobuf2/videobuf2-core.c index
> 0ca81d495bdaf..0234ddbfa4de2 100644
> --- a/drivers/media/common/videobuf2/videobuf2-core.c
> +++ b/drivers/media/common/videobuf2/videobuf2-core.c
> @@ -207,6 +207,10 @@ static int __vb2_buf_mem_alloc(struct vb2_buffer *vb)
> for (plane = 0; plane < vb->num_planes; ++plane) {
> unsigned long size = PAGE_ALIGN(vb->planes[plane].length);
>
> + /* Did it wrap around? */
> + if (size < vb->planes[plane].length)
> + goto free;
> +
> mem_priv = call_ptr_memop(vb, alloc,
> q->alloc_devs[plane] ? : q->dev,
> q->dma_attrs, size, q->dma_dir, q->gfp_flags);
Wouldn't it be better to reject length > INT_MAX (or some variations of that)
a few steps before, for instance just before calling __vb2_queue_alloc() ?
There's already a check in vb2_core_reqbufs():
/* Check that driver has set sane values */
if (WARN_ON(!num_planes))
return -EINVAL;
for (i = 0; i < num_planes; i++)
if (WARN_ON(!plane_sizes[i]))
return -EINVAL;
It could be extended to validate the sizes against wrap-around, and moved to a
separate function to be called in vb2_core_create_bufs() as well (as those
checks are missing there). Alternatively, the checks could be moved to the
beginning of __vb2_queue_alloc().
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2018-12-13 12:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-13 10:40 [PATCH 0/3] Videobuf2 corner case fixes Sakari Ailus
2018-12-13 10:40 ` [PATCH 1/3] videobuf2-core: Prevent size alignment wrapping buffer size to 0 Sakari Ailus
2018-12-13 11:22 ` Hans Verkuil
2018-12-13 12:49 ` Laurent Pinchart [this message]
2018-12-13 13:06 ` Sakari Ailus
2018-12-13 10:40 ` [PATCH 2/3] videobuf2-dma-sg: Prevent size from overflowing Sakari Ailus
2018-12-13 11:24 ` Hans Verkuil
2018-12-13 12:57 ` Laurent Pinchart
2018-12-13 13:00 ` Sakari Ailus
2018-12-13 13:03 ` Laurent Pinchart
2018-12-13 13:07 ` Sakari Ailus
2018-12-13 10:40 ` [PATCH 3/3] videobuf2-core.h: Document the alloc memop size argument as page aligned Sakari Ailus
2018-12-13 11:25 ` Hans Verkuil
2018-12-13 12:59 ` Laurent Pinchart
2018-12-13 13:02 ` Sakari Ailus
2018-12-13 13:08 ` 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=11116293.zm9aLRIdQE@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@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 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.