On Thu, 6 May 2021 15:08:08 +0800, Jay Fang wrote: > pch_spi_set_tx() frees data->pkt_tx_buff on failure of kzalloc() for > data->pkt_rx_buff, but its caller, pch_spi_process_messages(), will > free data->pkt_tx_buff again. Set data->pkt_tx_buff to NULL after > kfree() to avoid double free. Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next Thanks! [1/1] spi: spi-topcliff-pch: Fix potential double free in pch_spi_process_messages() commit: 026a1dc1af52742c5897e64a3431445371a71871 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