From: Cezary Rojewski <cezary.rojewski@intel.com>
To: Abdun Nihaal <nihaal@cse.iitm.ac.in>
Cc: <liam.r.girdwood@linux.intel.com>,
<peter.ujfalusi@linux.intel.com>,
<yung-chuan.liao@linux.intel.com>,
<ranjani.sridharan@linux.intel.com>,
<kai.vehmanen@linux.intel.com>, <pierre-louis.bossart@linux.dev>,
<broonie@kernel.org>, <perex@perex.cz>, <tiwai@suse.com>,
<linux-sound@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ASoC: intel: avs: Fix potential memory leak in avs_pci_probe()
Date: Thu, 13 Nov 2025 12:14:30 +0100 [thread overview]
Message-ID: <18c161e8-974b-4a4c-9ef2-c2cacef481b5@intel.com> (raw)
In-Reply-To: <20251113104121.79484-1-nihaal@cse.iitm.ac.in>
On 2025-11-13 11:41 AM, Abdun Nihaal wrote:
> In snd_hdac_ext_bus_get_ml_capabilities(), memory is allocated for
> multiple hdac_ext_link structures, and appended to bus->hlink_list.
> But the subsequent error paths in avs_pci_probe() don't free them.
>
> Fix this by calling snd_hdac_ext_link_free_all() on the error path.
> Also handle the return code of snd_hdac_ext_bus_get_ml_capabilities()
> correctly, since it can return -ENOMEM.
I'd suggest to be strict, no need for lengthy message when addressing
simple problem. Your title already answers _what_?, the message shall
answer _why_?. Example:
snd_hdac_ext_bus_get_ml_capabilities() may fail when allocating LINK
resources.
>
> Fixes: 1affc44ea5dd ("ASoC: Intel: avs: PCI driver implementation")
> Signed-off-by: Abdun Nihaal <nihaal@cse.iitm.ac.in>
> ---
> Compile tested only. Issue found using static analysis.
Well, it's good to do at least a simple functional test before sending,
see below.
>
> sound/soc/intel/avs/core.c | 11 +++++++++--
> 1 file changed, 9 insertions(+), 2 deletions(-)
>
> diff --git a/sound/soc/intel/avs/core.c b/sound/soc/intel/avs/core.c
> index 6e0e65584c7f..ece78a1c0e42 100644
> --- a/sound/soc/intel/avs/core.c
> +++ b/sound/soc/intel/avs/core.c
> @@ -473,8 +473,13 @@ static int avs_pci_probe(struct pci_dev *pci, const struct pci_device_id *id)
> }
>
> snd_hdac_bus_parse_capabilities(bus);
> - if (bus->mlcap)
> - snd_hdac_ext_bus_get_ml_capabilities(bus);
> + if (bus->mlcap) {
> + ret = snd_hdac_ext_bus_get_ml_capabilities(bus);
> + if (ret < 0) {
Just 'if (ret)' here.
> + dev_err(dev, "failed to get multilink capabilities: %d\n", ret);
> + goto err_ml_capabilities;
> + }
> + }
>
> if (dma_set_mask_and_coherent(dev, DMA_BIT_MASK(64)))
> dma_set_mask_and_coherent(dev, DMA_BIT_MASK(32));
> @@ -516,6 +521,8 @@ static int avs_pci_probe(struct pci_dev *pci, const struct pci_device_id *id)
> snd_hdac_bus_free_stream_pages(bus);
> snd_hdac_ext_stream_free_all(bus);
> err_init_streams:
> + snd_hdac_ext_link_free_all(bus);
> +err_ml_capabilities:
Don't believe that's correct. -ENOMEM may be returned when allocating
resources for an entry N>0. Skipping snd_hdac_ext_link_free_all() may
leave things at status quo - memory leak.
> iounmap(adev->dsp_ba);
> err_remap_bar4:
> iounmap(bus->remap_addr);
next prev parent reply other threads:[~2025-11-13 11:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-13 10:41 Abdun Nihaal
2025-11-13 11:14 ` Cezary Rojewski [this message]
2025-11-13 11:35 ` Abdun Nihaal
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=18c161e8-974b-4a4c-9ef2-c2cacef481b5@intel.com \
--to=cezary.rojewski@intel.com \
--cc=broonie@kernel.org \
--cc=kai.vehmanen@linux.intel.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=nihaal@cse.iitm.ac.in \
--cc=perex@perex.cz \
--cc=peter.ujfalusi@linux.intel.com \
--cc=pierre-louis.bossart@linux.dev \
--cc=ranjani.sridharan@linux.intel.com \
--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
all inboxes | Powered by JetHome®