linux-kernel - Re: [PATCH] ARM:dma-mapping: Handle DMA_BIDIRECTIONAL in _dma_page_cpu_to

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: <56407A82.6010504@arm.com>
Date:	Mon, 9 Nov 2015 10:50:42 +0000
From:	Robin Murphy <robin.murphy@....com>
To:	"Sharma, Sanjeev" <Sanjeev_Sharma@...tor.com>,
	Will Deacon <will.deacon@....com>,
	sanjeev sharma <sanjeevsharmaengg@...il.com>
Cc:	Russell King - ARM Linux <linux@....linux.org.uk>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	"m.szyprowski@...sung.com" <m.szyprowski@...sung.com>
Subject: Re: [PATCH] ARM:dma-mapping: Handle DMA_BIDIRECTIONAL in
 _dma_page_cpu_to_dev()

On 09/11/15 10:15, Sharma, Sanjeev wrote:
> On Mon, Nov 09, 2015 at 11:29:17AM +0530, sanjeev sharma wrote:
>>      On Wed, Nov 04, 2015 at 10:39:13AM +0000, Will Deacon wrote:
>>      > On Wed, Nov 04, 2015 at 03:26:48PM +0530, Sanjeev Sharma wrote:
>>      > > _dma_page_cpu_to_dev() treat DMA_BIDIRECTIONAL similar to
>>      > > DMA_TO_DEVICE which means that destination buffer is device
>>      > > memory,means cpu may have written some data to source buffer and
>>      > > data may be in cache line.For cleaner operation we need to call
>>      > > outer_flush_range() which will clean and invalidate outer cache lines.
>>      >
>>      > Why isn't the clean sufficient in this case? We're mapping the buffer
>>      > to the device, so we clean the dirty lines in the CPU caches and make
>>      > them visible to the device. If the CPU later wants to read the buffer
>>      > (i.e. after the device has DMA'd into it), you'll need to map the
>>      > buffer to the CPU, which will perform the invalidation of the CPU caches.
>>
>>      Indeed.  bidirectional mode is already handled prefectly well by this
>>      code.  No patches are required.
>>
>>      Thanks Russell & Will for providing input.
>>
>>      Let's assume , CPU don't read the buffer then there could be the problem
>>      correct ? IMO, to handle every use case outer_flush_range can be used ?
>>      If still it doesn't make sense to use flush on bidirectional mappings, then
>>      FIXME comment should be removed from the function to avoid any
>>      Confusion.
>>
>>
>>
>> Please let me know what you think on above comment ?
>
> I still don't understand the problem that you're trying to fix.
>
> It may cause the following issue.
> 1.we create the buffer with cache, and in some cases, the cache may be dirty.
> 2.then we call the sync_for_device function with flag DMA_BIDIRECTIONAL to avoid some cache problems.

This performs a cache clean, so the dirty lines are flushed out and 
cache and memory contents now match.

> 3. however __dma_page_cpu_to_dev() just see DMA_BIDIRECTIONAL the same as
> DMA_TO_DEVICE, which means the kernel will not invalid the cache if we use the flag DMA_BIDIRECTIONAL.

The CPU doesn't need to invalidate the cache at this point, since a) 
it's valid, and, crucially b) it will now refrain from accessing the 
buffer until the device has finished writing.

> 4.since the dirty cache is not invalid, the dirty content may be showed on the buffer in the future rendering.

The CPU _must_ call *_sync_for_cpu before it either reads or writes the 
buffer again. In this case, DMA_BIDIRECTIONAL is equivalent to 
DMA_FROM_DEVICE, thus will invalidate what the CPU still thinks are 
clean cache lines, so that whatever the device wrote to memory is then 
visible.

If you're seeing wrong data anywhere, that implies you have some 
necessary sync calls missing.

Robin.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/