diff options
| author | Christoph Hellwig <[email protected]> | 2024-12-04 09:42:40 +0900 |
|---|---|---|
| committer | Keith Busch <[email protected]> | 2024-12-04 09:23:11 -0800 |
| commit | ad0cf42e1fc4810170a8e8e232e85d69073e4d25 (patch) | |
| tree | f5d9c7b6be4965177199269fd65f7e0638bbc9f4 /tools/testing/selftests/bpf/prog_tests/autoload.c | |
| parent | 41d826c8a9de37af5d1710a37b55720bd5ad8709 (diff) | |
nvme-pci: don't use dma_alloc_noncontiguous with 0 merge boundary
Only call into nvme_alloc_host_mem_single which uses
dma_alloc_noncontiguous when there is non-null dma merge boundary.
Without this we'll call into dma_alloc_noncontiguous for device using
dma-direct, which can work fine as long as the preferred size is below the
MAX_ORDER of the page allocator, but blows up with a warning if it is
too large.
Fixes: 63a5c7a4b4c4 ("nvme-pci: use dma_alloc_noncontigous if possible")
Reported-by: Leon Romanovsky <[email protected]>
Reported-by: Chaitanya Kumar Borah <[email protected]>
Signed-off-by: Christoph Hellwig <[email protected]>
Reviewed-by: Leon Romanovsky <[email protected]>
Tested-by: Chaitanya Kumar Borah <[email protected]>
Signed-off-by: Keith Busch <[email protected]>
Diffstat (limited to 'tools/testing/selftests/bpf/prog_tests/autoload.c')
0 files changed, 0 insertions, 0 deletions