[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZuGAwQGPWdpO1-G9@iZbp1asjb3cy8ks0srf007Z>
Date: Wed, 11 Sep 2024 19:36:33 +0800
From: Qianqiang Liu <qianqiang.liu@....com>
To: Mark Brown <broonie@...nel.org>
Cc: amergnat@...libre.com, angelogioacchino.delregno@...labora.com,
lgirdwood@...il.com, matthias.bgg@...il.com,
linux-sound@...r.kernel.org, linux-mediatek@...ts.infradead.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ASoC: mt8365: Fix using uninitialized value "i2s_data"
issue
On Wed, Sep 11, 2024 at 11:52:58AM +0100, Mark Brown wrote:
> On Wed, Sep 11, 2024 at 08:15:17AM +0800, Qianqiang Liu wrote:
>
> >
> > spin_lock_irqsave(&afe_priv->afe_ctrl_lock, flags);
> >
> > + if (!i2s_data) {
> > + spin_unlock_irqrestore(&afe_priv->afe_ctrl_lock, flags);
> > + return;
> > + }
> > +
>
> Why would we look up i2s_data without the lock, take the lock, then
> check if we actually found it? That doesn't seem right.
Just check the "i2s_data" is NULL or not.
--
Best,
Qianqiang Liu
Powered by blists - more mailing lists