linux/arch/xtensa
Christoph Hellwig 518a2f1925 dma-mapping: zero memory returned from dma_alloc_*
If we want to map memory from the DMA allocator to userspace it must be
zeroed at allocation time to prevent stale data leaks.   We already do
this on most common architectures, but some architectures don't do this
yet, fix them up, either by passing GFP_ZERO when we use the normal page
allocator or doing a manual memset otherwise.

Signed-off-by: Christoph Hellwig <hch@lst.de>
Acked-by: Geert Uytterhoeven <geert@linux-m68k.org> [m68k]
Acked-by: Sam Ravnborg <sam@ravnborg.org> [sparc]
2018-12-20 08:13:52 +01:00
..
boot xtensa: add NOTES section to the linker script 2018-10-29 19:02:08 -07:00
configs xtensa: drop unused {CONFIG,PLATFORM}_DEFAULT_MEM_SIZE 2018-08-20 12:27:52 -07:00
include Xtensa fixes for v4.20-rc3 2018-11-16 10:10:27 -06:00
kernel dma-mapping: zero memory returned from dma_alloc_* 2018-12-20 08:13:52 +01:00
lib xtensa: add support for KASAN 2017-12-16 22:37:12 -08:00
mm Xtensa fixes and cleanups for v4.20: 2018-11-01 14:32:43 -07:00
oprofile License cleanup: add SPDX GPL-2.0 license identifier to files with no license 2017-11-02 11:10:55 +01:00
platforms memblock: stop using implicit alignment to SMP_CACHE_BYTES 2018-10-31 08:54:16 -07:00
variants xtensa: add test_kc705_be variant 2018-08-20 12:34:45 -07:00
Kconfig dma-mapping: always build the direct mapping code 2018-12-13 21:06:11 +01:00
Kconfig.debug Kconfig: consolidate the "Kernel hacking" menu 2018-08-02 08:06:48 +09:00
Makefile Devicetree updates for 4.20: 2018-10-26 12:09:58 -07:00