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	c6x: enable building all dtbs	2018-10-02 09:23:21 -05:00
configs	c6x: defconfig: Cleanup from old Kconfig options	2017-08-24 09:34:01 -04:00
include	treewide: remove current_text_addr	2018-10-31 08:54:12 -07:00
kernel	c6x changes for 4.20	2018-10-31 15:39:25 -07:00
lib	C6X: library code	2011-10-06 19:48:23 -04:00
mm	dma-mapping: zero memory returned from dma_alloc_*	2018-12-20 08:13:52 +01:00
platforms	c6x: fix platforms/plldata.c get_coreid build error	2018-04-10 09:58:38 -04: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	kbuild: consolidate Devicetree dtb build rules	2018-10-02 09:23:21 -05:00