From: Souptick Joarder <jrdr.linux@gmail.com>
To: Russell King - ARM Linux <linux@armlinux.org.uk>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Matthew Wilcox <willy@infradead.org>,
Michal Hocko <mhocko@suse.com>,
pawel@osciak.com, Marek Szyprowski <m.szyprowski@samsung.com>,
Kyungmin Park <kyungmin.park@samsung.com>,
mchehab@kernel.org, robin.murphy@arm.com,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
Linux-MM <linux-mm@kvack.org>
Subject: Re: [PATCH v5 7/9] videobuf2/videobuf2-dma-sg.c: Convert to use vm_insert_range
Date: Wed, 2 Jan 2019 21:22:34 +0530 [thread overview]
Message-ID: <CAFqt6zadJ-4xh256BqzALnGY31nDAU=5XwUaSaz5OcJuOc7Bfg@mail.gmail.com> (raw)
Message-ID: <20190102155234.tFOr1Pa4nr113DVy-rVOsL37oMRTys6whiEq73isDCQ@z> (raw)
In-Reply-To: <20190102111553.GG26090@n2100.armlinux.org.uk>
On Wed, Jan 2, 2019 at 4:46 PM Russell King - ARM Linux
<linux@armlinux.org.uk> wrote:
>
> On Wed, Jan 02, 2019 at 04:23:15PM +0530, Souptick Joarder wrote:
> > On Mon, Dec 24, 2018 at 6:53 PM Souptick Joarder <jrdr.linux@gmail.com> wrote:
> > >
> > > Convert to use vm_insert_range to map range of kernel memory
> > > to user vma.
> > >
> > > Signed-off-by: Souptick Joarder <jrdr.linux@gmail.com>
> > > Reviewed-by: Matthew Wilcox <willy@infradead.org>
> > > Acked-by: Marek Szyprowski <m.szyprowski@samsung.com>
> > > Acked-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
> > > ---
> > > drivers/media/common/videobuf2/videobuf2-dma-sg.c | 23 +++++++----------------
> > > 1 file changed, 7 insertions(+), 16 deletions(-)
> > >
> > > diff --git a/drivers/media/common/videobuf2/videobuf2-dma-sg.c b/drivers/media/common/videobuf2/videobuf2-dma-sg.c
> > > index 015e737..898adef 100644
> > > --- a/drivers/media/common/videobuf2/videobuf2-dma-sg.c
> > > +++ b/drivers/media/common/videobuf2/videobuf2-dma-sg.c
> > > @@ -328,28 +328,19 @@ static unsigned int vb2_dma_sg_num_users(void *buf_priv)
> > > static int vb2_dma_sg_mmap(void *buf_priv, struct vm_area_struct *vma)
> > > {
> > > struct vb2_dma_sg_buf *buf = buf_priv;
> > > - unsigned long uaddr = vma->vm_start;
> > > - unsigned long usize = vma->vm_end - vma->vm_start;
> > > - int i = 0;
> > > + unsigned long page_count = vma_pages(vma);
> > > + int err;
> > >
> > > if (!buf) {
> > > printk(KERN_ERR "No memory to map\n");
> > > return -EINVAL;
> > > }
> > >
> > > - do {
> > > - int ret;
> > > -
> > > - ret = vm_insert_page(vma, uaddr, buf->pages[i++]);
> > > - if (ret) {
> > > - printk(KERN_ERR "Remapping memory, error: %d\n", ret);
> > > - return ret;
> > > - }
> > > -
> > > - uaddr += PAGE_SIZE;
> > > - usize -= PAGE_SIZE;
> > > - } while (usize > 0);
> > > -
> > > + err = vm_insert_range(vma, vma->vm_start, buf->pages, page_count);
> > > + if (err) {
> > > + printk(KERN_ERR "Remapping memory, error: %d\n", err);
> > > + return err;
> > > + }
> > >
> >
> > Looking into the original code -
> > drivers/media/common/videobuf2/videobuf2-dma-sg.c
> >
> > Inside vb2_dma_sg_alloc(),
> > ...
> > buf->num_pages = size >> PAGE_SHIFT;
> > buf->dma_sgt = &buf->sg_table;
> >
> > buf->pages = kvmalloc_array(buf->num_pages, sizeof(struct page *),
> > GFP_KERNEL | __GFP_ZERO);
> > ...
> >
> > buf->pages has index upto *buf->num_pages*.
> >
> > now inside vb2_dma_sg_mmap(),
> >
> > unsigned long usize = vma->vm_end - vma->vm_start;
> > int i = 0;
> > ...
> > do {
> > int ret;
> >
> > ret = vm_insert_page(vma, uaddr, buf->pages[i++]);
> > if (ret) {
> > printk(KERN_ERR "Remapping memory, error:
> > %d\n", ret);
> > return ret;
> > }
> >
> > uaddr += PAGE_SIZE;
> > usize -= PAGE_SIZE;
> > } while (usize > 0);
> > ...
> > is it possible for any value of *i > (buf->num_pages)*,
> > buf->pages[i] is going to overrun the page boundary ?
>
> Yes it is, and you've found an array-overrun condition that is
> triggerable from userspace - potentially non-root userspace too.
> Depending on what it can cause to be mapped without oopsing the
> kernel, it could be very serious. At best, it'll oops the kernel.
> At worst, it could expose pages of memory that userspace should
> not have access to.
>
> This is why I've been saying that we need a helper that takes the
> _object_ and the user request, and does all the checking internally,
> so these kinds of checks do not get overlooked.
ok, while replacing this code with the suggested vm_insert_range_buggy(),
we could fixed this issue.
>
> A good API is one that helpers authors avoid bugs.
>
> --
> RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
> FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up
> According to speedtest.net: 11.9Mbps down 500kbps up
next prev parent reply other threads:[~2019-01-02 15:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-24 13:26 Souptick Joarder
2018-12-24 13:26 ` Souptick Joarder
2019-01-02 10:53 ` Souptick Joarder
2019-01-02 10:53 ` Souptick Joarder
2019-01-02 11:15 ` Russell King - ARM Linux
2019-01-02 15:52 ` Souptick Joarder [this message]
2019-01-02 15:52 ` Souptick Joarder
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='CAFqt6zadJ-4xh256BqzALnGY31nDAU=5XwUaSaz5OcJuOc7Bfg@mail.gmail.com' \
--to=jrdr.linux@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux@armlinux.org.uk \
--cc=m.szyprowski@samsung.com \
--cc=mchehab@kernel.org \
--cc=mhocko@suse.com \
--cc=pawel@osciak.com \
--cc=robin.murphy@arm.com \
--cc=willy@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox