spi: fsi: Fix transfer returning without finalizing message
Subsystems (2)
Eddie James
maintainerPATCH 1/1 spi: fsi: Fix transfer returning without finalizing message
In the case that the SPI mux isn't set, the transfer_one_message function returns without finalizing the message. This means that the transfer never completes, resulting in hung tasks and an eventual kernel panic. Fix it by finalizing the transfer in this case.
--- drivers/spi/spi-fsi.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/spi/spi-fsi.c +1 -1
@@ -477,7 +477,7 @@ static int fsi_spi_transfer_one_message(struct spi_controller *ctlr, rc =fsi_spi_check_mux (ctx->fsi, ctx->dev);if (rc) -return rc; + goto error;list_for_each_entry (transfer, &mesg->transfers, transfer_list) {struct fsi_spi_sequence seq;
Signature · 1 line
2.26.2
Quoted 9 lines · Eddie James
In the case that the SPI mux isn't set, the
transfer_one_messagefunction returns without finalizing the message. This means that the transfer never completes, resulting in hung tasks and an eventual kernel panic. Fix it by finalizing the transfer in this case.Fixes 9211a441e606 ("spi: fsi: Check mux status before transfers")Signed-off-by Eddie James <[email protected]>
Quoted 20 lines
--- drivers/spi/spi-fsi.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)drivers/spi/spi-fsi.c +1
-2@@ -477,7 +477,7 @@ static int fsi_spi_transfer_one_message(struct spi_controller *ctlr, rc =fsi_spi_check_mux (ctx->fsi, ctx->dev);if (rc) -return rc; + goto error;list_for_each_entry (transfer, &mesg->transfers, transfer_list) {struct fsi_spi_sequence seq; --2.26.2
Mark Brown
maintainerQuoted 5 lines · Eddie James
In the case that the SPI mux isn't set, the
transfer_one_messagefunction returns without finalizing the message. This means that the transfer never completes, resulting in hung tasks and an eventual kernel panic. Fix it by finalizing the transfer in this case.
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/1] spi: fsi: Fix transfer returning without finalizing message
commit: ee4ad5d06509b3aea79b6a77bebd09ef891bed8d
All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying to this mail.
Thanks,
Mark