Linux-Amlogic Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Ethan Tidmore" <ethantidmore06@gmail.com>
Cc: neil.armstrong@linaro.org, linux-amlogic@lists.infradead.org
Subject: Re: [PATCH] ASoC: meson: aiu: Fix resource leak
Date: Tue, 07 Jul 2026 01:34:36 +0000	[thread overview]
Message-ID: <20260707013437.27DA61F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260707012424.1661733-1-ethantidmore06@gmail.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The patch modifies the error path to purportedly free the `aiu-formatter` resource by jumping to the `err` label, referencing commit 83b83024cdbfd. However, the `aiu-formatter` allocation and cleanup code (specifically `gx_formatter_create` and `gx_formatter_free`) does not exist in the codebase at this revision. The patch is a "ghost fix" attempting to resolve a resource leak for a feature that is missing in this tree.
--

--- Patch [1]: [PATCH] ASoC: meson: aiu: Fix resource leak ---
commit e1f43f4a59c62657488472af87aa2e5d80576b03
Author: Ethan Tidmore <ethantidmore06@gmail.com>

ASoC: meson: aiu: Fix resource leak

This commit changes an error path in aiu_probe() to use a goto label
instead of returning directly. The commit message indicates this is to
ensure the aiu-formatter is properly freed when component registration
fails.

> diff --git a/sound/soc/meson/aiu.c b/sound/soc/meson/aiu.c
> index f2890111c1d2c..1cfa165fb9cfc 100644
> --- a/sound/soc/meson/aiu.c
> +++ b/sound/soc/meson/aiu.c

[ ... ]

> @@ -288,7 +288,7 @@ static int aiu_probe(struct platform_device *pdev)
>  					 ARRAY_SIZE(aiu_cpu_dai_drv));
>  	if (ret) {
>  		dev_err(dev, "Failed to register cpu component\n");
> -		return ret;
> +		goto err;

[Severity: Medium]
Is there a missing dependency for this patch, or is it an incomplete
backport?

The commit message mentions that the aiu-formatter is not being freed.
However, looking at aiu_probe() in this tree, there is no aiu-formatter
allocation or cleanup code present anywhere in the function.

>  	}
>  
>  	/* Register the hdmi codec control component */

[ ... ]

>  err:
>  	snd_soc_unregister_component(dev);
>  	return ret;
>  }

[Severity: Medium]
At this error label, only snd_soc_unregister_component() is called,
and no formatter cleanup logic exists. Does this fix apply to a
different tree where the formatter feature is actually present?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260707012424.1661733-1-ethantidmore06@gmail.com?part=1

_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic

  reply	other threads:[~2026-07-07  1:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-07  1:24 [PATCH] ASoC: meson: aiu: Fix resource leak Ethan Tidmore
2026-07-07  1:34 ` sashiko-bot [this message]
2026-07-07  1:41   ` Ethan Tidmore
2026-07-07 20:33 ` Valerio Setti
2026-07-10 11:27   ` Markus Elfring
2026-07-10 12:47     ` Valerio Setti

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=20260707013437.27DA61F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=ethantidmore06@gmail.com \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=neil.armstrong@linaro.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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