From: Robin Murphy <robin.murphy@arm.com>
To: Souptick Joarder <jrdr.linux@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Matthew Wilcox <willy@infradead.org>,
Michal Hocko <mhocko@suse.com>,
joro@8bytes.org, Linux-MM <linux-mm@kvack.org>,
iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 6/9] iommu/dma-iommu.c: Convert to use vm_insert_range
Date: Mon, 10 Dec 2018 16:31:45 +0000 [thread overview]
Message-ID: <67137be3-c56f-fb01-5ebe-86e9ebf5714b@arm.com> (raw)
In-Reply-To: <CAFqt6zYF5fFQuGFGss3D1q=jKJGPOD33XLmZiAkBFT9zx_55LA@mail.gmail.com>
On 07/12/2018 20:41, Souptick Joarder wrote:
> On Fri, Dec 7, 2018 at 7:17 PM Robin Murphy <robin.murphy@arm.com> wrote:
>>
>> On 06/12/2018 18:43, Souptick Joarder 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>
>>> ---
>>> drivers/iommu/dma-iommu.c | 13 +++----------
>>> 1 file changed, 3 insertions(+), 10 deletions(-)
>>>
>>> diff --git a/drivers/iommu/dma-iommu.c b/drivers/iommu/dma-iommu.c
>>> index d1b0475..a2c65e2 100644
>>> --- a/drivers/iommu/dma-iommu.c
>>> +++ b/drivers/iommu/dma-iommu.c
>>> @@ -622,17 +622,10 @@ struct page **iommu_dma_alloc(struct device *dev, size_t size, gfp_t gfp,
>>>
>>> int iommu_dma_mmap(struct page **pages, size_t size, struct vm_area_struct *vma)
>>> {
>>> - unsigned long uaddr = vma->vm_start;
>>> - unsigned int i, count = PAGE_ALIGN(size) >> PAGE_SHIFT;
>>> - int ret = -ENXIO;
>>> + unsigned long count = PAGE_ALIGN(size) >> PAGE_SHIFT;
>>>
>>> - for (i = vma->vm_pgoff; i < count && uaddr < vma->vm_end; i++) {
>>> - ret = vm_insert_page(vma, uaddr, pages[i]);
>>> - if (ret)
>>> - break;
>>> - uaddr += PAGE_SIZE;
>>> - }
>>> - return ret;
>>> + return vm_insert_range(vma, vma->vm_start,
>>> + pages + vma->vm_pgoff, count);
>>
>> You also need to adjust count to compensate for the pages skipped by
>> vm_pgoff, otherwise you've got an out-of-bounds dereference triggered
>> from userspace, which is pretty high up the "not good" scale (not to
>> mention the entire call would then propagate -EFAULT back from
>> vm_insert_page() and thus always appear to fail for nonzero offsets).
>
> So this should something similar to ->
>
> return vm_insert_range(vma, vma->vm_start,
> pages + vma->vm_pgoff, count - vma->vm_pgoff);
>
Yup, I think that looks appropriate.
Robin.
prev parent reply other threads:[~2018-12-10 16:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-06 18:43 Souptick Joarder
2018-12-07 13:47 ` Robin Murphy
2018-12-07 20:41 ` Souptick Joarder
2018-12-10 16:31 ` Robin Murphy [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=67137be3-c56f-fb01-5ebe-86e9ebf5714b@arm.com \
--to=robin.murphy@arm.com \
--cc=akpm@linux-foundation.org \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=jrdr.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.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