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/dts	DeviceTree for 4.15:	2017-11-14 18:25:40 -08:00
configs	openrisc: add simple_smp dts and defconfig for simulators	2017-11-03 14:01:15 +09:00
include	treewide: remove current_text_addr	2018-10-31 08:54:12 -07:00
kernel	dma-mapping: zero memory returned from dma_alloc_*	2018-12-20 08:13:52 +01:00
lib	OpenRISC updates for v4.15	2017-11-13 12:12:00 -08:00
mm	mm: remove include/linux/bootmem.h	2018-10-31 08:54:16 -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	kbuild: remove redundant LDFLAGS clearing in arch/*/Makefile	2018-07-19 08:40:27 +09:00