diff options
| author | Christoph Hellwig <hch@lst.de> | 2022-12-20 09:05:36 +0100 |
|---|---|---|
| committer | Christoph Hellwig <hch@lst.de> | 2022-12-21 08:45:17 +0100 |
| commit | db918321275d648294a3fb2bdefeb99e33f00467 (patch) | |
| tree | 0e413d82500070cfe72f05ee03717f51629bbd76 /lib/mpi/mpi-inline.h | |
| parent | 6feb57c2fd7c787aecf2846a535248899e7b70fa (diff) | |
| download | linux-stable-db918321275d648294a3fb2bdefeb99e33f00467.tar.gz linux-stable-db918321275d648294a3fb2bdefeb99e33f00467.tar.bz2 linux-stable-db918321275d648294a3fb2bdefeb99e33f00467.zip | |
ALSA: memalloc: don't use GFP_COMP for non-coherent dma 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 ffcb75458460 that flag stopped being cleared for all
dma allocations, but only got rejected for coherent ones.
Start fixing this by not requesting __GFP_COMP in the sound code, which
is the only place that did this.
Fixes: ffcb75458460 ("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>
Diffstat (limited to 'lib/mpi/mpi-inline.h')
0 files changed, 0 insertions, 0 deletions