[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <58928aec02be483e8a188fcc6e53d805a24534aa.camel@linux.intel.com>
Date: Mon, 22 May 2023 13:28:30 -0700
From: Ranjani Sridharan <ranjani.sridharan@...ux.intel.com>
To: Harshit Mogalapalli <harshit.m.mogalapalli@...cle.com>,
Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>,
Liam Girdwood <lgirdwood@...il.com>,
Peter Ujfalusi <peter.ujfalusi@...ux.intel.com>,
Bard Liao <yung-chuan.liao@...ux.intel.com>,
Kai Vehmanen <kai.vehmanen@...ux.intel.com>,
Daniel Baluta <daniel.baluta@....com>,
Mark Brown <broonie@...nel.org>,
Jaroslav Kysela <perex@...ex.cz>,
Takashi Iwai <tiwai@...e.com>,
Rander Wang <rander.wang@...el.com>,
Jyri Sarha <jyri.sarha@...el.com>,
sound-open-firmware@...a-project.org, alsa-devel@...a-project.org,
linux-kernel@...r.kernel.org
Cc: error27@...il.com, dan.carpenter@...aro.org,
kernel-janitors@...r.kernel.org
Subject: Re: [PATCH next] ASoC: SOF: Intel: hda-dai: Fix locking in
hda_ipc4_pre_trigger()
On Thu, 2023-05-18 at 23:44 -0700, Harshit Mogalapalli wrote:
> hda_ipc4_pre_trigger() has two issues:
> 1. In the default case, we are returning without unlocking the
> mutex.
> 2. In case SNDRV_PCM_TRIGGER_STOP: when ret is less than zero it
> goes
> to out, unlocks but returns zero instead of a negative value.
>
> Fix this by changing the final return value to 'ret' instead of zero,
> and initialize 'ret' to zero in the start of the function.
>
> Fixes: 225f37b578a9 ("ASoC: SOF: ipc4-pcm: reset all pipelines during
> FE DAI hw_free")
> Signed-off-by: Harshit Mogalapalli <harshit.m.mogalapalli@...cle.com>
> ---
> Only compile tested. This is found using static anlysis with Smatch.
> ---
Thanks for this fix. LGTM.
Reviewed-by: Ranjani Sridharan <ranjani.sridharan@...ux.intel.com>
Powered by blists - more mailing lists