linux-kernel - Re: [PATCH] staging: ion: make the pte default none PTE

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20160115232334.GD19062@n2100.arm.linux.org.uk>
Date:	Fri, 15 Jan 2016 23:23:34 +0000
From:	Russell King - ARM Linux <linux@....linux.org.uk>
To:	Laura Abbott <labbott@...hat.com>
Cc:	Chen Feng <puck.chen@...ilicon.com>, gregkh@...uxfoundation.org,
	arve@...roid.com, riandrews@...roid.com,
	paul.gortmaker@...driver.com, gioh.kim@....com,
	tranmanphong@...il.com, mitchelh@...eaurora.org,
	devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org,
	yudongbin@...ilicon.com, saberlily.xia@...ilicon.com,
	suzhuangluan@...ilicon.com, kong.kongxinwei@...ilicon.com,
	xuyiping@...ilicon.com, z.liuxinliang@...ilicon.com,
	weidong2@...ilicon.com, w.f@...wei.com, puck.chen@...mail.com,
	shimingxing@...ilicon.com, oliver.fu@...ilicon.com,
	albert.lubing@...ilicon.com, chenxiang9@...wei.com,
	liuzixing@...wei.com, haojian.zhuang@...aro.org,
	Catalin Marinas <catalin.marinas@....com>,
	Will Deacon <will.deacon@....com>, dan.zhao@...ilicon.com,
	peter.panshilin@...ilicon.com, linuxarm@...wei.com,
	dev@...ts.96boards.org, qijiwen@...ilicon.com,
	linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH] staging: ion: make the pte default none PTE_RDONLY

On Fri, Jan 15, 2016 at 03:03:42PM -0800, Laura Abbott wrote:
> (adding linux-arm and a few people)
> 
> On 01/14/2016 06:42 PM, Chen Feng wrote:
> >The page is already alloc at ion_alloc function,
> >ion_mmap map the alloced pages to user-space.
> >
> >The default prot can be PTE_RDONLY. Take a look at
> >here:
> >set_pte_at()
> >arch/arm64/include/asm:
> >		if (pte_dirty(pte) && pte_write(pte))
> >			pte_val(pte) &= ~PTE_RDONLY;
> >		else
> >			pte_val(pte) |= PTE_RDONLY;
> >
> >So with the dirty bit,it can improve the efficiency
> >and donnot need to handle memory fault when use access.
> >
> >Signed-off-by: Chen Feng <puck.chen@...ilicon.com>
> >Signed-off-by: Wei Dong <weidong2@...ilicon.com>
> >Reviewed-by: Zhuangluan Su <suzhuangluan@...ilicon.com>
> >---
> >  drivers/staging/android/ion/ion.c | 3 +++
> >  1 file changed, 3 insertions(+)
> >
> >diff --git a/drivers/staging/android/ion/ion.c b/drivers/staging/android/ion/ion.c
> >index e237e9f..dba5942 100644
> >--- a/drivers/staging/android/ion/ion.c
> >+++ b/drivers/staging/android/ion/ion.c
> >@@ -1026,6 +1026,9 @@ static int ion_mmap(struct dma_buf *dmabuf, struct vm_area_struct *vma)
> >  	if (!(buffer->flags & ION_FLAG_CACHED))
> >  		vma->vm_page_prot = pgprot_writecombine(vma->vm_page_prot);
> >
> >+	/*Default writeable*/
> >+	vma->vm_page_prot = pte_mkdirty(vma->vm_page_prot);
> >+
> >  	mutex_lock(&buffer->lock);
> >  	/* now map it to userspace */
> >  	ret = buffer->heap->ops->map_user(buffer->heap, buffer, vma);
> >
> 
> The extra fault is unfortunate but I'm skeptical about just setting
> pte_mkdirty.
> 
> Catalin/Will, do you have any thoughts? Right now it seems like any
> range mapped with remap_pfn_range will have this extra fault
> behavior. Is marking the range dirty the best solution?

What happens if the mapping requested was read only - at the very
least, I don't think this should be done unconditionally.

-- 
RMK's Patch system: http://www.arm.linux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.