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	microblaze: enable building all dtbs	2018-10-02 09:23:21 -05:00
configs	microblaze: Enabling CONFIG_BRIDGE in mmu_defconfig	2017-06-22 15:36:59 +02:00
include	s390 updates for 4.20-rc2	2018-11-09 06:30:44 -06:00
kernel	Devicetree updates for 4.20:	2018-10-26 12:09:58 -07:00
lib	microblaze: Setup dependencies for ASM optimized lib functions	2018-03-16 12:51:26 +01:00
mm	dma-mapping: zero memory returned from dma_alloc_*	2018-12-20 08:13:52 +01:00
oprofile	License cleanup: add SPDX GPL-2.0 license identifier to files with no license	2017-11-02 11:10:55 +01:00
pci	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
Kconfig.platform	microblaze: Setup dependencies for ASM optimized lib functions	2018-03-16 12:51:26 +01:00
Makefile	kbuild: consolidate Devicetree dtb build rules	2018-10-02 09:23:21 -05:00