From: 김승우 <sw0312.kim@samsung.com>
To: Marek Szyprowski <m.szyprowski@samsung.com>
Cc: linux-media@vger.kernel.org, mchehab@redhat.com,
pawel@osciak.com, kyungmin.park@samsung.com,
sw0312.kim@samsung.com
Subject: Re: [PATCH] media: vb2: add length check for mmap
Date: Thu, 18 Apr 2013 11:53:24 +0900 [thread overview]
Message-ID: <516F6024.3020806@samsung.com> (raw)
In-Reply-To: <5167A3A3.5090200@samsung.com>
Oops, there is a issue.
vb2-core does not PAGE_ALIGN to length of buffer, but mmap() always do
PAGE_ALIGN to its length.
So non PAGE_ALIGN length of buffer from driver side can not mmaped with
this patch.
On 2013년 04월 12일 15:03, Marek Szyprowski wrote:
>
> On 4/12/2013 5:57 AM, Seung-Woo Kim wrote:
>> The length of mmap() can be bigger than length of vb2 buffer, so
>> it should be checked.
>>
>> Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com>
>
> Acked-by: Marek Szyprowski <m.szyprowski@samsung.com>
>
>> ---
>> drivers/media/v4l2-core/videobuf2-core.c | 5 +++++
>> 1 files changed, 5 insertions(+), 0 deletions(-)
>>
>> diff --git a/drivers/media/v4l2-core/videobuf2-core.c
>> b/drivers/media/v4l2-core/videobuf2-core.c
>> index db1235d..2c6ff2d 100644
>> --- a/drivers/media/v4l2-core/videobuf2-core.c
>> +++ b/drivers/media/v4l2-core/videobuf2-core.c
>> @@ -1886,6 +1886,11 @@ int vb2_mmap(struct vb2_queue *q, struct
>> vm_area_struct *vma)
>> vb = q->bufs[buffer];
>> + if (vb->v4l2_planes[plane].length < (vma->vm_end -
>> vma->vm_start)) {
>> + dprintk(1, "Invalid length\n");
>> + return -EINVAL;
>> + }
>> +
>> ret = call_memop(q, mmap, vb->planes[plane].mem_priv, vma);
>> if (ret)
>> return ret;
>
> Best regards
--
Seung-Woo Kim
Samsung Software R&D Center
--
prev parent reply other threads:[~2013-04-18 2:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-12 3:57 [PATCH] media: vb2: add length check for mmap Seung-Woo Kim
2013-04-12 6:03 ` Marek Szyprowski
2013-04-16 10:21 ` Laurent Pinchart
2013-04-18 2:53 ` 김승우 [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=516F6024.3020806@samsung.com \
--to=sw0312.kim@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-media@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mchehab@redhat.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;
as well as URLs for NNTP newsgroup(s).