linux-kernel - Re: How to make mmap'ed kernel buffer non-cacheable

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: <462C3554.5000906@yahoo.com.au>
Date:	Mon, 23 Apr 2007 14:25:56 +1000
From:	Nick Piggin <nickpiggin@...oo.com.au>
To:	Bhuvan Kumar MITTAL <bhuvan.mittal@...com>
CC:	'Alan Cox' <alan@...rguk.ukuu.org.uk>, linux-kernel@...r.kernel.org
Subject: Re: How to make mmap'ed kernel buffer non-cacheable

Bhuvan Kumar MITTAL wrote:
> Hi Alan,
> 
> I believe that dma_alloc_coherent will mark the kernel buffer as uncached at alocation time. 
> But that is not my intention. I have mapped some user space memory to the kernel buffer and I wish to ensure that the contents of both are coherent and correctly ordered. 
> 
> In other words I wish to flush the contents of the kernel buffer to user space as soon as new data is available in my kernel buffer. How to do that? Will doing mysnc from the user space help?

msync is only for pagecache. If you modify user mapped RAM from the kernel, or wish
to read user modified RAM from the kernel, you should issue a flush_dcache_page after
and before, respectively. See Documentation/cachetlb.h.

Does that fix it? What are the details of your platform?

-- 
SUSE Labs, Novell Inc.
-
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/