diff options
| author | Christoph Hellwig | 2018-03-28 15:35:35 +0200 |
|---|---|---|
| committer | Thomas Gleixner | 2018-03-28 17:34:23 +0200 |
| commit | e89f5b37015309a8bdf0b21d08007580b92f92a4 (patch) | |
| tree | 194c925657ddd394d26ccc1ae707ffdac31c8534 /drivers/iommu | |
| parent | Merge branch 'linus' into x86/dma, to resolve a conflict with upstream (diff) | |
| download | kernel-qcow2-linux-e89f5b37015309a8bdf0b21d08007580b92f92a4.tar.gz kernel-qcow2-linux-e89f5b37015309a8bdf0b21d08007580b92f92a4.tar.xz kernel-qcow2-linux-e89f5b37015309a8bdf0b21d08007580b92f92a4.zip | |
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
Diffstat (limited to 'drivers/iommu')
0 files changed, 0 insertions, 0 deletions