diff options
| author | Halil Pasic <pasic@linux.ibm.com> | 2024-10-07 22:10:30 +0200 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2024-12-05 14:01:10 +0100 |
| commit | 88f52359dab777768bbe6118bf4f3d09a9cc3ce3 (patch) | |
| tree | 5254f9df6a301c6859f3d5440157c536c088c267 /scripts/cleanpatch | |
| parent | 50b81b50a991930f46452e0a19d6428632e77a7c (diff) | |
| download | linux-88f52359dab777768bbe6118bf4f3d09a9cc3ce3.tar.gz linux-88f52359dab777768bbe6118bf4f3d09a9cc3ce3.tar.bz2 linux-88f52359dab777768bbe6118bf4f3d09a9cc3ce3.zip | |
s390/virtio_ccw: Fix dma_parm pointer not set up
[ Upstream commit 14c7579376279e507e52bf022192b46097a55377 ]
At least since commit 334304ac2bac ("dma-mapping: don't return errors
from dma_set_max_seg_size") setting up device.dma_parms is basically
mandated by the DMA API. As of now Channel (CCW) I/O in general does not
utilize the DMA API, except for virtio. For virtio-ccw however the
common virtio DMA infrastructure is such that most of the DMA stuff
hinges on the virtio parent device, which is a CCW device.
So lets set up the dma_parms pointer for the CCW parent device and hope
for the best!
Fixes: 334304ac2bac ("dma-mapping: don't return errors from dma_set_max_seg_size")
Reported-by: Marc Hartmayer <mhartmay@linux.ibm.com>
Reviewed-by: Eric Farman <farman@linux.ibm.com>
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
Tested-by: Marc Hartmayer <mhartmay@linux.ibm.com>
Link: https://lore.kernel.org/r/20241007201030.204028-1-pasic@linux.ibm.com
Signed-off-by: Halil Pasic <pasic@linux.ibm.com>
Signed-off-by: Heiko Carstens <hca@linux.ibm.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'scripts/cleanpatch')
0 files changed, 0 insertions, 0 deletions
