From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: "Péter Ujfalusi" <peter.ujfalusi@linux.intel.com>,
"Amadeusz Sławiński" <amadeuszx.slawinski@linux.intel.com>,
"Mark Brown" <broonie@kernel.org>
Cc: Cezary Rojewski <cezary.rojewski@intel.com>,
Takashi Iwai <tiwai@suse.com>, Jaroslav Kysela <perex@perex.cz>,
alsa-devel@alsa-project.org, linux-sound@vger.kernel.org
Subject: Re: [PATCH] ASoC: topology: Fix route memory corruption
Date: Thu, 13 Jun 2024 16:13:52 +0200 [thread overview]
Message-ID: <27668c46-5a44-4e14-8219-5fba6a5c4610@linux.intel.com> (raw)
In-Reply-To: <0fdbae0e-e540-4c35-a555-5b2607526115@linux.intel.com>
On 6/13/24 13:11, Péter Ujfalusi wrote:
>
>
> On 13/06/2024 12:01, Amadeusz Sławiński wrote:
>> It was reported that recent fix for memory corruption during topology
>> load, causes corruption in other cases. Instead of being overeager with
>> checking topology, assume that it is properly formatted and just
>> duplicate strings.
>
> Reviewed-by: Peter Ujfalusi <peter.ujfalusi@linux.intel.com>
Test results look much better indeed with
https://github.com/thesofproject/linux/pull/5057
Tested-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
>
>> Reported-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
>> Closes: https://lore.kernel.org/linux-sound/171812236450.201359.3019210915105428447.b4-ty@kernel.org/T/#m8c4bd5abf453960fde6f826c4b7f84881da63e9d
>> Suggested-by: Péter Ujfalusi <peter.ujfalusi@linux.intel.com>
>> Signed-off-by: Amadeusz Sławiński <amadeuszx.slawinski@linux.intel.com>
>> ---
>> sound/soc/soc-topology.c | 12 +++---------
>> 1 file changed, 3 insertions(+), 9 deletions(-)
>>
>> diff --git a/sound/soc/soc-topology.c b/sound/soc/soc-topology.c
>> index 0225bc5fc425a..4b166294602fa 100644
>> --- a/sound/soc/soc-topology.c
>> +++ b/sound/soc/soc-topology.c
>> @@ -1052,21 +1052,15 @@ static int soc_tplg_dapm_graph_elems_load(struct soc_tplg *tplg,
>> break;
>> }
>>
>> - route->source = devm_kmemdup(tplg->dev, elem->source,
>> - min(strlen(elem->source), maxlen),
>> - GFP_KERNEL);
>> - route->sink = devm_kmemdup(tplg->dev, elem->sink,
>> - min(strlen(elem->sink), maxlen),
>> - GFP_KERNEL);
>> + route->source = devm_kstrdup(tplg->dev, elem->source, GFP_KERNEL);
>> + route->sink = devm_kstrdup(tplg->dev, elem->sink, GFP_KERNEL);
>> if (!route->source || !route->sink) {
>> ret = -ENOMEM;
>> break;
>> }
>>
>> if (strnlen(elem->control, maxlen) != 0) {
>> - route->control = devm_kmemdup(tplg->dev, elem->control,
>> - min(strlen(elem->control), maxlen),
>> - GFP_KERNEL);
>> + route->control = devm_kstrdup(tplg->dev, elem->control, GFP_KERNEL);
>> if (!route->control) {
>> ret = -ENOMEM;
>> break;
>
next prev parent reply other threads:[~2024-06-13 14:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-13 9:01 [PATCH] ASoC: topology: Fix route memory corruption Amadeusz Sławiński
2024-06-13 11:11 ` Péter Ujfalusi
2024-06-13 14:13 ` Pierre-Louis Bossart [this message]
2024-06-14 9:24 ` Mark Brown
2024-06-14 14:16 ` Mark Brown
2024-08-13 17:11 ` Joakim Tjernlund
2024-08-15 7:23 ` Joakim Tjernlund
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=27668c46-5a44-4e14-8219-5fba6a5c4610@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=amadeuszx.slawinski@linux.intel.com \
--cc=broonie@kernel.org \
--cc=cezary.rojewski@intel.com \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=peter.ujfalusi@linux.intel.com \
--cc=tiwai@suse.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox