Skip to contentSkip to conversation

ASoC: SOF: ipc-msg-injector: Use devm_kzalloc() for the rx_buffer

PATCH In review Peter Ujfalusi 2 participants 2 messages Mar 9, 2022 – Mar 10, 2022

Subsystems (3)
lore
Share & tools
lore

Peter Ujfalusi

author maintainer
#0 lore raw

PATCH 1/1 ASoC: SOF: ipc-msg-injector: Use devm_kzalloc() for the rx_buffer

The rx_buffer is cleared before sending an IPC to make sure that when the /sys/kernel/debug/sof/ipc_msg_inject file is read we will have correct information in the buffer (no random or stale data).

But if the user reads the file before sending any message the buffer might contain garbage which should not be interpreted.

To prevent this, clear the rx_buffer on allocation.

Fixes cac0b0887e53 ("ASoC: SOF: Convert the generic IPC message injector into SOF client")
---
 sound/soc/sof/sof-client-ipc-msg-injector.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
sound/soc/sof/sof-client-ipc-msg-injector.c +1 -1
index bce103da4c49..dba6cfd7db09 100644
@@ -137,7 +137,7 @@ static int sof_msg_inject_probe(struct auxiliary_device *auxdev,
 		return -ENOMEM;
 
 	priv->tx_buffer = devm_kmalloc(dev, SOF_IPC_MSG_MAX_SIZE, GFP_KERNEL);
-	priv->rx_buffer = devm_kmalloc(dev, SOF_IPC_MSG_MAX_SIZE, GFP_KERNEL);
+	priv->rx_buffer = devm_kzalloc(dev, SOF_IPC_MSG_MAX_SIZE, GFP_KERNEL);
 	if (!priv->tx_buffer || !priv->rx_buffer)
 		return -ENOMEM;
 
Signature · 1 line
2.35.1
maintainer
#1 lore raw
Quoted 8 lines · Peter Ujfalusi

The rx_buffer is cleared before sending an IPC to make sure that when the /sys/kernel/debug/sof/ipc_msg_inject file is read we will have correct information in the buffer (no random or stale data).

But if the user reads the file before sending any message the buffer might contain garbage which should not be interpreted.

[...]

Applied to

https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next

Thanks!

[1/1] ASoC: SOF: ipc-msg-injector: Use devm_kzalloc() for the rx_buffer

      commit: 81acac8c2c88764c773811d1ec858852f81eb88a

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