All of lore.kernel.org
 help / color / mirror / Atom feed
From: 朱灿灿 <zhucancan@vivo.com>
To: Colin King <colin.king@canonical.com>
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
	kernel-janitors@vger.kernel.org, Takashi Iwai <tiwai@suse.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>
Subject: Re:[PATCH][next] ASoC: soc-pcm: Fix uninitialised return value in variable ret
Date: Mon, 11 Jan 2021 17:56:37 +0800 (GMT+08:00)	[thread overview]
Message-ID: <AJsAUwACDs*x8qLUpTvPvKqR.3.1610358997320.Hmail.zhucancan@vivo.com> (raw)
In-Reply-To: <20210108123546.19601-1-colin.king@canonical.com>

Agree, thanks.


>
>Currently when attempting to start the BE fails because the
>FE is not started the error return variable ret is not initialized
>and garbage is returned.  Fix this by setting it to 0 so the
>caller does not report the error "ASoC: failed to shutdown some BEs"
>and because this failure path has already reported the reason for
>the early return.
>
>Addresses-Coverity: ("Uninitialized scalar variable")
>Fixes: 2c1382840c19 ("ASoC: soc-pcm: disconnect BEs if the FE is not ready")
>Signed-off-by: Colin Ian King <colin.king@canonical.com>
>---
> sound/soc/soc-pcm.c | 1 +
> 1 file changed, 1 insertion(+)
>
>diff --git a/sound/soc/soc-pcm.c b/sound/soc/soc-pcm.c
>index 481a4a25acb0..b787ce4ceb5a 100644
>--- a/sound/soc/soc-pcm.c
>+++ b/sound/soc/soc-pcm.c
>@@ -2443,6 +2443,7 @@ static int dpcm_run_update_startup(struct snd_soc_pcm_runtime *fe, int stream)
> 		fe->dpcm[stream].state == SND_SOC_DPCM_STATE_CLOSE) {
> 		dev_err(fe->dev, "ASoC: FE %s is not ready %d\n",
> 			fe->dai_link->name, fe->dpcm[stream].state);
>+		ret = 0;
> 		goto disconnect;
> 	}
> 
>-- 
>2.29.2
>





  reply	other threads:[~2021-01-11  9:57 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-08 12:35 [PATCH][next] ASoC: soc-pcm: Fix uninitialised return value in variable ret Colin King
2021-01-08 12:35 ` Colin King
2021-01-11  9:56 ` 朱灿灿 [this message]
2021-01-11 16:35 ` Mark Brown
2021-01-11 16:35   ` Mark Brown
2021-01-11 17:07   ` Colin Ian King
2021-01-11 17:07     ` Colin Ian King
2021-01-11 17:09     ` Mark Brown
2021-01-11 17:09       ` Mark Brown
2021-01-11 17:37   ` Colin Ian King
2021-01-11 17:37     ` Colin Ian King
2021-01-11 17:58     ` Mark Brown
2021-01-11 17:58       ` Mark Brown
2021-01-12 10:22     ` Dan Carpenter
2021-01-12 10:22       ` Dan Carpenter
2021-01-12 10:22       ` Dan Carpenter
2021-01-12 10:24       ` Colin Ian King
2021-01-12 10:24         ` Colin Ian King

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='AJsAUwACDs*x8qLUpTvPvKqR.3.1610358997320.Hmail.zhucancan@vivo.com' \
    --to=zhucancan@vivo.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=colin.king@canonical.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.