dma-mapping: Don't clear GFP_ZERO in dma_alloc_attrs
authorChristoph Hellwig <hch@lst.de>
Wed, 28 Mar 2018 13:35:35 +0000 (15:35 +0200)
committerThomas Gleixner <tglx@linutronix.de>
Wed, 28 Mar 2018 15:34:23 +0000 (17:34 +0200)
commite89f5b37015309a8bdf0b21d08007580b92f92a4
tree194c925657ddd394d26ccc1ae707ffdac31c8534
parentea2301b6220117398a1de4f4bc853fbe886d5e08
dma-mapping: Don't clear GFP_ZERO in dma_alloc_attrs

Revert the clearing of __GFP_ZERO in dma_alloc_attrs and move it to
dma_direct_alloc for now.  While most common architectures always zero dma
cohereny allocations (and x86 did so since day one) this is not documented
and at least arc and s390 do not zero without the explicit __GFP_ZERO
argument.

Fixes: 57bf5a8963f8 ("dma-mapping: clear harmful GFP_* flags in common code")
Reported-by: Evgeniy Didin <Evgeniy.Didin@synopsys.com>
Reported-by: Sebastian Ott <sebott@linux.vnet.ibm.com>
Signed-off-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Tested-by: Evgeniy Didin <Evgeniy.Didin@synopsys.com>
Cc: iommu@lists.linux-foundation.org
Link: https://lkml.kernel.org/r/20180328133535.17302-2-hch@lst.de
include/linux/dma-mapping.h
lib/dma-direct.c