From: patchwork-bot+linux-amlogic@kernel.org
To: Colin King <colin.king@canonical.com>
Cc: linux-amlogic@lists.infradead.org, khilman@kernel.org
Subject: Re: [PATCH] ASoC: meson: fix memory leak of links if allocation of ldata fails
Date: Tue, 07 Jul 2020 18:51:11 +0000 [thread overview]
Message-ID: <159414787183.3387.5104845479572791462.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20200604171216.60043-1-colin.king@canonical.com>
Hello:
This patch was applied to khilman/linux-amlogic.git (refs/heads/for-next).
On Thu, 4 Jun 2020 18:12:16 +0100 you wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> Currently if the allocation of ldata fails the error return path
> does not kfree the allocated links object. Fix this by adding
> an error exit return path that performs the necessary kfree'ing.
>
> Addresses-Coverity: ("Resource leak")
> Fixes: 7864a79f37b5 ("ASoC: meson: add axg sound card support")
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
>
> [...]
Here is a summary with links:
- ASoC: meson: fix memory leak of links if allocation of ldata fails
https://git.kernel.org/khilman/linux-amlogic/c/6e801dc411329aff592fbd48fb116183d0acdb00
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.wiki.kernel.org/userdoc/pwbot
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
prev parent reply other threads:[~2020-07-07 18:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-04 17:12 [PATCH] ASoC: meson: fix memory leak of links if allocation of ldata fails Colin King
2020-06-07 20:39 ` Jerome Brunet
2020-06-08 12:46 ` Mark Brown
2020-07-07 18:51 ` patchwork-bot+linux-amlogic [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=159414787183.3387.5104845479572791462.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-amlogic@kernel.org \
--cc=colin.king@canonical.com \
--cc=khilman@kernel.org \
--cc=linux-amlogic@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).