summaryrefslogtreecommitdiffstats
path: root/samples
diff options
context:
space:
mode:
authorMarek Szyprowski <m.szyprowski@samsung.com>2015-04-23 12:46:16 +0100
committerWill Deacon <will.deacon@arm.com>2015-04-27 11:39:50 +0100
commit6829e274a623187c24f7cfc0e3d35f25d087fcc5 (patch)
treea6ca873b29878ee7bc8c328af8a64bae0f49a37e /samples
parent6544e67bfb1bf55bcf3c0f6b37631917e9acfb74 (diff)
downloadop-kernel-dev-6829e274a623187c24f7cfc0e3d35f25d087fcc5.zip
op-kernel-dev-6829e274a623187c24f7cfc0e3d35f25d087fcc5.tar.gz
arm64: dma-mapping: always clear allocated buffers
Buffers allocated by dma_alloc_coherent() are always zeroed on Alpha, ARM (32bit), MIPS, PowerPC, x86/x86_64 and probably other architectures. It turned out that some drivers rely on this 'feature'. Allocated buffer might be also exposed to userspace with dma_mmap() call, so clearing it is desired from security point of view to avoid exposing random memory to userspace. This patch unifies dma_alloc_coherent() behavior on ARM64 architecture with other implementations by unconditionally zeroing allocated buffer. Cc: <stable@vger.kernel.org> # v3.14+ Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com> Signed-off-by: Will Deacon <will.deacon@arm.com>
Diffstat (limited to 'samples')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud