dma-mapping: reject GFP_COMP for noncoherent allocations
While not quite as bogus as for the dma-coherent allocations that were fixed earlier, GFP_COMP for these allocations has no benefits for the dma-direct case, and can't be supported at all by dma dma-iommu backend which splits up allocations into smaller orders. Due to an oversight in ffcb7545 that flag stopped being cleared for all dma allocations, but only got rejected for coherent ones, so fix up these callers to not allow __GFP_COMP as well after the sound code has been fixed to not ask for it. Fixes: ffcb7545 ("dma-mapping: reject __GFP_COMP in dma_alloc_attrs") Reported-by:Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com> Reported-by:
Kai Vehmanen <kai.vehmanen@linux.intel.com> Signed-off-by:
Christoph Hellwig <hch@lst.de> Acked-by:
Takashi Iwai <tiwai@suse.de> Tested-by:
Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com> Tested-by:
Kai Vehmanen <kai.vehmanen@linux.intel.com>
parent
db918321
Please register or sign in to comment