From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: alsa-devel@alsa-project.org, kernel-janitors@vger.kernel.org,
Takashi Iwai <tiwai@suse.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH] ASoC: dapm: Fix a couple uninitialized ret variables
Date: Mon, 10 Sep 2018 14:22:24 +0000 [thread overview]
Message-ID: <20180910142224.GJ1653@imbe.wolfsonmicro.main> (raw)
In-Reply-To: <20180907194033.cmt4rdiwwznaeudq@kili.mountain>
On Fri, Sep 07, 2018 at 10:40:33PM +0300, Dan Carpenter wrote:
> Smatch complains that these variables could be uninitialized. The first
> one in snd_soc_dai_link_event() is probably a false positive, because
> probably we know the lists are not empty. I would normally ignore the
> warning, but GCC complains here as well so I just silenced the warning.
> The "ret" in snd_soc_dapm_new_dai() does need to be initialized or it
> leads to a bogus dereference in the caller.
>
> Fixes: 3bbf5d34fd4a ("ASoC: dapm: Move error handling to snd_soc_dapm_new_control_unlocked")
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
>
> diff --git a/sound/soc/soc-dapm.c b/sound/soc/soc-dapm.c
> index 9f4edcd19e02..0dcdcc23dcfd 100644
> --- a/sound/soc/soc-dapm.c
> +++ b/sound/soc/soc-dapm.c
> @@ -3623,7 +3623,7 @@ static int snd_soc_dai_link_event(struct snd_soc_dapm_widget *w,
> struct snd_pcm_hw_params *params = NULL;
> struct snd_pcm_runtime *runtime = NULL;
> unsigned int fmt;
> - int ret;
> + int ret = 0;
This one got fixed the other day in fc269c039644 ("ASoC: dapm:
Avoid uninitialised variable warning").
>
> config = rtd->dai_link->params + rtd->params_select;
>
> @@ -3938,8 +3938,10 @@ snd_soc_dapm_new_dai(struct snd_soc_card *card, struct snd_soc_pcm_runtime *rtd,
> dev_dbg(card->dev, "ASoC: adding %s widget\n", link_name);
>
> w = snd_soc_dapm_new_control_unlocked(&card->dapm, &template);
> - if (IS_ERR(w))
> + if (IS_ERR(w)) {
> + ret = PTR_ERR(w);
> goto outfree_kcontrol_news;
> + }
Thanks for spotting this, looks good to me.
Reviewed-by: Charles Keepax <ckeepax@opensource.cirrus.com>
>
> w->priv = rtd;
>
Thanks,
Charles
prev parent reply other threads:[~2018-09-10 14:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-07 19:40 [PATCH] ASoC: dapm: Fix a couple uninitialized ret variables Dan Carpenter
2018-09-10 14:22 ` Charles Keepax [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=20180910142224.GJ1653@imbe.wolfsonmicro.main \
--to=ckeepax@opensource.cirrus.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=dan.carpenter@oracle.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=lgirdwood@gmail.com \
--cc=tiwai@suse.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