From: "Péter Ujfalusi" <peter.ujfalusi@linux.intel.com>
To: Kunwu Chan <chentao@kylinos.cn>,
pierre-louis.bossart@linux.intel.com, lgirdwood@gmail.com,
yung-chuan.liao@linux.intel.com,
ranjani.sridharan@linux.intel.com, daniel.baluta@nxp.com,
kai.vehmanen@linux.intel.com, broonie@kernel.org, perex@perex.cz,
tiwai@suse.com, chao.song@intel.com
Cc: kunwu.chan@hotmail.com, sound-open-firmware@alsa-project.org,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ASoC: SOF: Fix null pointer dereference in sof_pci_probe
Date: Tue, 5 Dec 2023 11:44:16 +0200 [thread overview]
Message-ID: <74ba8770-6174-4820-8dc4-e97e5814e665@linux.intel.com> (raw)
In-Reply-To: <55c00bb3-b795-4698-ba3f-56d10df1882a@kylinos.cn>
On 05/12/2023 11:10, Kunwu Chan wrote:
> It's my bad, i'll follow your suggestion in v2 patch:
> 1. remove 'Fixes: 46207ca24545' label
>
> 2. rename subject to 'ASoC: SOF: Add null pointer check to sof_pci_probe'
>
> 3. when sof_pdata->fw_filename_prefix is NULL,don't use it to dev_dbg.
> Or just use a
> if (sof_pdata->fw_filename_prefix)
> dev_dbg(dev,
> "Platform uses community key, changed fw path to %s\n",
> sof_pdata->fw_filename_prefix);
> else
> dev_dbg(dev,
> "Platform uses community key, changed fw path to %s/%s\n",
> sof_pdata->desc->default_fw_path[sof_pdata->ipc_type],
> "community");
>
> Is it okay to modify it like this?
The code has been rewritten and all of these issues have been
eliminated, fixed in core SOF.
>
>
> Thanks,
> Kunwu
>
> On 2023/12/4 19:34, Péter Ujfalusi wrote:
>>
>>
>> On 23/11/2023 17:54, Kunwu Chan wrote:
>>> devm_kasprintf() returns a pointer to dynamically allocated memory
>>> which can be NULL upon failure.
>>>
>>> Fixes: 46207ca24545 ("ASoC: SOF: pci: change the default firmware
>>> path when the community key is used")
>>> Fixes: 25bbc0c59ee1 ("ASoC: SOF: Add path definition for external
>>> firmware libraries")
>>> Signed-off-by: Kunwu Chan <chentao@kylinos.cn>
>>
>> This patch cannot fix both commits as at 46207ca24545 the lib path was
>> not present.
>> Please don't bundle unrelated fixes, it makes maintainers life harder.
>>
>> As a note: if the allocation fails it is not going to cause null
>> dereference as the code checks !sof_pdata->*_prefix to see if it is
>> provided (override) or not (use default).
>> At most it will cause the kernel to 'ignore' the path override, but if
>> this allocation fails this is least of our problem ;)
>>
>>> ---
>>> sound/soc/sof/sof-pci-dev.c | 8 ++++++++
>>> 1 file changed, 8 insertions(+)
>>>
>>> diff --git a/sound/soc/sof/sof-pci-dev.c b/sound/soc/sof/sof-pci-dev.c
>>> index 64b326e3ef85..75a9bfa5bfbe 100644
>>> --- a/sound/soc/sof/sof-pci-dev.c
>>> +++ b/sound/soc/sof/sof-pci-dev.c
>>> @@ -282,6 +282,10 @@ int sof_pci_probe(struct pci_dev *pci, const
>>> struct pci_device_id *pci_id)
>>> devm_kasprintf(dev, GFP_KERNEL, "%s/%s",
>>>
>>> sof_pdata->desc->default_fw_path[sof_pdata->ipc_type],
>>> "community");
>>> + if (!sof_pdata->fw_filename_prefix) {
>>> + ret = -ENOMEM;
>>> + goto out;
>>> + }
>>> dev_dbg(dev,
>>> "Platform uses community key, changed fw path to %s\n",
>>> @@ -303,6 +307,10 @@ int sof_pci_probe(struct pci_dev *pci, const
>>> struct pci_device_id *pci_id)
>>> devm_kasprintf(dev, GFP_KERNEL, "%s/%s",
>>>
>>> sof_pdata->desc->default_lib_path[sof_pdata->ipc_type],
>>> "community");
>>> + if (!sof_pdata->fw_lib_prefix) {
>>> + ret = -ENOMEM;
>>> + goto out;
>>> + }
>>> dev_dbg(dev,
>>> "Platform uses community key, changed fw_lib path
>>> to %s\n",
>>
--
Péter
prev parent reply other threads:[~2023-12-05 9:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-23 15:54 [PATCH] ASoC: SOF: Fix null pointer dereference in sof_pci_probe Kunwu Chan
2023-12-04 11:34 ` Péter Ujfalusi
2023-12-04 12:38 ` Mark Brown
2023-12-05 9:12 ` Kunwu Chan
[not found] ` <1701766721668457.408.seg@mailgw>
2023-12-05 9:10 ` Kunwu Chan
2023-12-05 9:44 ` Péter Ujfalusi [this message]
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=74ba8770-6174-4820-8dc4-e97e5814e665@linux.intel.com \
--to=peter.ujfalusi@linux.intel.com \
--cc=broonie@kernel.org \
--cc=chao.song@intel.com \
--cc=chentao@kylinos.cn \
--cc=daniel.baluta@nxp.com \
--cc=kai.vehmanen@linux.intel.com \
--cc=kunwu.chan@hotmail.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=sound-open-firmware@alsa-project.org \
--cc=tiwai@suse.com \
--cc=yung-chuan.liao@linux.intel.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