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 v2] ASoC: intel: avs: Fix potential memory leak in avs_pci_probe()
Date: Thu, 13 Nov 2025 14:11:19 +0100 [thread overview]
Message-ID: <24e5abed-9084-4f3d-b620-e272164f687e@intel.com> (raw)
In-Reply-To: <20251113120447.86911-1-nihaal@cse.iitm.ac.in>
On 2025-11-13 1:04 PM, Abdun Nihaal wrote:
> The link resources allocated in snd_hdac_ext_bus_get_ml_capabilities()
> are not freed on subsequent error paths in avs_pci_probe().
>
> Fixes: 1affc44ea5dd ("ASoC: Intel: avs: PCI driver implementation")
> Signed-off-by: Abdun Nihaal <nihaal@cse.iitm.ac.in>
Reviewed-by: Cezary Rojewski <cezary.rojewski@intel.com>
> ---
>
> v1->v2:
> - Shorten commit message
> - Handle the case when some of the links are allocated, as pointed out
> by Cezary Rojewski
>
> Link to V1:
> https://lore.kernel.org/all/20251113104121.79484-1-nihaal@cse.iitm.ac.in/T/#u
>
> sound/soc/intel/avs/core.c | 14 ++++++++++----
> 1 file changed, 10 insertions(+), 4 deletions(-)
>
> diff --git a/sound/soc/intel/avs/core.c b/sound/soc/intel/avs/core.c
> index 6e0e65584c7f..f0d77f3f3a28 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);
After giving this a second thought, I believe
snd_hdac_ext_bus_get_ml_capabilities() is the offender here - the
function should have freed whatever its already allocated before
returning an error, not count on the caller to free the resources
instead. In other words, the fix should update the callee too.
However, one may say that it's a separate issue. I'm fine with existing
patch landing as-is. Can prepare separate a change that covers problem
mentioned by me above. The cons is: additional 1-2 LOC traffic for the
avs-driver code.
I leave the decision to Mark, I'm OK with both approaches.
> + if (ret) {
> + 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));
> @@ -483,7 +488,7 @@ static int avs_pci_probe(struct pci_dev *pci, const struct pci_device_id *id)
> ret = avs_hdac_bus_init_streams(bus);
> if (ret < 0) {
> dev_err(dev, "failed to init streams: %d\n", ret);
> - goto err_init_streams;
> + goto err_ml_capabilities;
> }
>
> ret = avs_hdac_acquire_irq(adev);
> @@ -515,7 +520,8 @@ static int avs_pci_probe(struct pci_dev *pci, const struct pci_device_id *id)
> err_acquire_irq:
> snd_hdac_bus_free_stream_pages(bus);
> snd_hdac_ext_stream_free_all(bus);
> -err_init_streams:
> +err_ml_capabilities:
> + snd_hdac_ext_link_free_all(bus);
> iounmap(adev->dsp_ba);
> err_remap_bar4:
> iounmap(bus->remap_addr);
next prev parent reply other threads:[~2025-11-13 13:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-13 12:04 [PATCH v2] ASoC: intel: avs: Fix potential memory leak in avs_pci_probe() Abdun Nihaal
2025-11-13 13:11 ` Cezary Rojewski [this message]
2025-11-21 8:55 ` Cezary Rojewski
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=24e5abed-9084-4f3d-b620-e272164f687e@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