* [PATCH] ASoC: SOF: ipc-msg-injector: Use devm_kzalloc() for the rx_buffer
@ 2022-03-09 11:01 Peter Ujfalusi
2022-03-10 11:35 ` Mark Brown
0 siblings, 1 reply; 2+ messages in thread
From: Peter Ujfalusi @ 2022-03-09 11:01 UTC (permalink / raw)
To: lgirdwood, broonie, pierre-louis.bossart
Cc: alsa-devel, yung-chuan.liao, ranjani.sridharan, kai.vehmanen
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")
Signed-off-by: Peter Ujfalusi <peter.ujfalusi@linux.intel.com>
Reviewed-by: Bard Liao <yung-chuan.liao@linux.intel.com>
Reviewed-by: Ranjani Sridharan <ranjani.sridharan@linux.intel.com>
Reviewed-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
---
sound/soc/sof/sof-client-ipc-msg-injector.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sound/soc/sof/sof-client-ipc-msg-injector.c b/sound/soc/sof/sof-client-ipc-msg-injector.c
index bce103da4c49..dba6cfd7db09 100644
--- a/sound/soc/sof/sof-client-ipc-msg-injector.c
+++ b/sound/soc/sof/sof-client-ipc-msg-injector.c
@@ -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;
--
2.35.1
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH] ASoC: SOF: ipc-msg-injector: Use devm_kzalloc() for the rx_buffer
2022-03-09 11:01 [PATCH] ASoC: SOF: ipc-msg-injector: Use devm_kzalloc() for the rx_buffer Peter Ujfalusi
@ 2022-03-10 11:35 ` Mark Brown
0 siblings, 0 replies; 2+ messages in thread
From: Mark Brown @ 2022-03-10 11:35 UTC (permalink / raw)
To: Peter Ujfalusi, pierre-louis.bossart, lgirdwood
Cc: alsa-devel, yung-chuan.liao, ranjani.sridharan, kai.vehmanen
On Wed, 9 Mar 2022 13:01:04 +0200, Peter Ujfalusi wrote:
> 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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2022-03-10 11:37 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2022-03-09 11:01 [PATCH] ASoC: SOF: ipc-msg-injector: Use devm_kzalloc() for the rx_buffer Peter Ujfalusi
2022-03-10 11:35 ` Mark Brown
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).