From: Cezary Rojewski <cezary.rojewski@intel.com>
To: Guangshuo Li <lgs201920130244@gmail.com>
Cc: <stable@vger.kernel.org>,
Liam Girdwood <liam.r.girdwood@linux.intel.com>,
Peter Ujfalusi <peter.ujfalusi@linux.intel.com>,
Bard Liao <yung-chuan.liao@linux.intel.com>,
Kai Vehmanen <kai.vehmanen@linux.intel.com>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.dev>,
Mark Brown <broonie@kernel.org>,
"Jaroslav Kysela" <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Thorsten Blum <thorsten.blum@linux.dev>,
<linux-sound@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ASoC: Intel: SST: fix platform device leak on probe failure
Date: Mon, 21 Sep 2026 11:31:06 +0200 [thread overview]
Message-ID: <dd60ce64-4af1-479e-99d3-1787a06da882@intel.com> (raw)
In-Reply-To: <20260921073847.63505-1-lgs201920130244@gmail.com>
On 9/21/2026 9:38 AM, Guangshuo Li wrote:
> sst_acpi_probe() registers platform devices for the SST platform and
> machine drivers using platform_device_register_data(), but does not
> unregister them when later probe steps fail.
s/machine drivers/machine board/
The above paragraph alone is sufficient, please drop everything else in
the commit message. There is no need to write wall-of-text for a fix
addressing a missing error path. In case this wall was provided by an
agent, relevant Assisted-by: tag is needed in the tag area.
You can keep the very last sentence if you want to.
> If machine device registration fails, the already registered SST platform
> device is left registered. The same leak happens when
> sst_platform_get_resources() or sst_context_init() fails after both
> platform devices have been successfully registered.
>
> A registered platform device owns resources allocated by the platform
> device core and must be released with platform_device_unregister() so
> that the device reference is dropped and platform_device_release() can
> free the backing platform_object.
>
> Unregister the created platform devices on all failure paths to restore
> the missing cleanup.
>
> The issue was identified by a static analysis tool I developed and
> confirmed by manual review.
>
> Fixes: caf94ed8629a ("ASoC: Intel: bytcr_rt5640: fixup DAI codec_name with HID")
> Cc: stable@vger.kernel.org
> Signed-off-by: Guangshuo Li <lgs201920130244@gmail.com>
For the commit title: please update to:
ASoC: Intel: atom: Fix (...)
Provided both the commit title and message are updated, feel free to add:
Reviewed-by: Cezary Rojewski <cezary.rojewski@intel.com>
> ---
> sound/soc/intel/atom/sst/sst_acpi.c | 13 ++++++++++---
> 1 file changed, 10 insertions(+), 3 deletions(-)
>
> diff --git a/sound/soc/intel/atom/sst/sst_acpi.c b/sound/soc/intel/atom/sst/sst_acpi.c
> index 73624e1b138a..a1f16083bd3d 100644
> --- a/sound/soc/intel/atom/sst/sst_acpi.c
> +++ b/sound/soc/intel/atom/sst/sst_acpi.c
> @@ -352,7 +352,8 @@ static int sst_acpi_probe(struct platform_device *pdev)
> if (IS_ERR(mdev)) {
> dev_err(dev, "Failed to create machine device: %s\n",
> mach->drv_name);
> - return PTR_ERR(mdev);
> + ret = PTR_ERR(mdev);
> + goto err_unregister_plat_dev;
> }
>
> /* Fill sst platform data */
> @@ -361,15 +362,21 @@ static int sst_acpi_probe(struct platform_device *pdev)
>
> ret = sst_platform_get_resources(ctx);
> if (ret)
> - return ret;
> + goto err_unregister_mdev;
>
> ret = sst_context_init(ctx);
> if (ret < 0)
> - return ret;
> + goto err_unregister_mdev;
>
> sst_configure_runtime_pm(ctx);
> platform_set_drvdata(pdev, ctx);
> return ret;
> +
> +err_unregister_mdev:
> + platform_device_unregister(mdev);
> +err_unregister_plat_dev:
> + platform_device_unregister(plat_dev);
> + return ret;
> }
Looks like sst_acpi_remove() does not unregister the devices either.
That could be fixed by enlisting devm_add_action_or_reset() in
sst_acpi_probe() without altering sst_acpi_remove() at all.
Would you mind sending a separate patch updating the function so both
the error path and the driver-unload clean up the device objects?
Kind regards,
Czarek
next prev parent reply other threads:[~2026-09-21 9:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 7:38 Guangshuo Li
2026-09-21 9:31 ` Cezary Rojewski [this message]
2026-09-22 8:17 ` Guangshuo Li
2026-09-21 15:06 ` krzk
2026-09-22 2:47 ` Guangshuo Li
2026-09-21 15:09 ` krzk
2026-09-21 15:12 ` krzk
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=dd60ce64-4af1-479e-99d3-1787a06da882@intel.com \
--to=cezary.rojewski@intel.com \
--cc=broonie@kernel.org \
--cc=kai.vehmanen@linux.intel.com \
--cc=lgs201920130244@gmail.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=peter.ujfalusi@linux.intel.com \
--cc=pierre-louis.bossart@linux.dev \
--cc=stable@vger.kernel.org \
--cc=thorsten.blum@linux.dev \
--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®