Re: [PATCH] spi: fsl-lpspi: replace dmaengine_terminate_all with dmaengine_terminate_sync

[sashiko-bot@kernel.org]

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Critical] Missing termination of the active RX DMA channel when TX DMA preparation fails, leading to potential memory corruption.
--

commit ec7592d39a6caaca48276f43db4b9a0f4fa50bfd
Author: Carlos Song <carlos.song@nxp.com>
spi: fsl-lpspi: replace dmaengine_terminate_all with dmaengine_terminate_sync

This commit replaces the deprecated dmaengine_terminate_all() API with
dmaengine_terminate_sync() in the fsl-lpspi driver.

> diff --git a/drivers/spi/spi-fsl-lpspi.c b/drivers/spi/spi-fsl-lpspi.c
> index e201309f8aae3..1a94a42fac319 100644
> --- a/drivers/spi/spi-fsl-lpspi.c
> +++ b/drivers/spi/spi-fsl-lpspi.c
[ ... ]
> @@ -647,7 +647,7 @@ static int fsl_lpspi_dma_transfer(struct spi_controller *controller,
>  				tx->sgl, tx->nents, DMA_MEM_TO_DEV,
>  				DMA_PREP_INTERRUPT | DMA_CTRL_ACK);
>  	if (!desc_tx) {
> -		dmaengine_terminate_all(controller->dma_tx);
> +		dmaengine_terminate_sync(controller->dma_tx);

Because controller->dma_rx was already submitted and issued just prior to
preparing desc_tx, does this error path also need to terminate the RX
channel?

If dmaengine_prep_slave_sg fails for the TX channel and the driver returns
-EINVAL, the SPI core will abort the transfer and unmap the buffers. Since
controller->dma_rx is still running, could this cause the DMA controller to
write to freed or unmapped memory?

This wasn't introduced by your patch, but modifying this exact error path
might be a good opportunity to fix the missing RX channel cleanup.

>  		return -EINVAL;
>  	}

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260519104517.2794390-1-carlos.song@oss.nxp.com?part=1