[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20220927115619.GA4547@lxhi-065>
Date: Tue, 27 Sep 2022 13:56:19 +0200
From: Eugeniu Rosca <erosca@...adit-jv.com>
To: Amadeusz Sławiński
<amadeuszx.slawinski@...ux.intel.com>
CC: Eugeniu Rosca <erosca@...adit-jv.com>,
Liam Girdwood <lgirdwood@...il.com>,
Mark Brown <broonie@...nel.org>,
Jaroslav Kysela <perex@...ex.cz>,
Takashi Iwai <tiwai@...e.com>, <alsa-devel@...a-project.org>,
<linux-kernel@...r.kernel.org>,
Yanmin Zhang <yanmin_zhang@...ux.intel.com>,
Eugeniu Rosca <roscaeugeniu@...il.com>,
Jiada Wang <jiada_wang@...tor.com>,
Zhang Yanmin <yanmin.zhang@...el.com>,
Ramesh Babu <ramesh.babu@...el.com>,
Dean Jenkins <Dean_Jenkins@...tor.com>,
Ramesh Babu B <ramesh.babu.b@...el.com>,
xiao jin <jin.xiao@...el.com>,
Cezary Rojewski <cezary.rojewski@...el.com>
Subject: Re: [PATCH] ASoC: soc-pcm: fix fe and be race when accessing
substream->runtime
Hello Amadeusz,
On Di, Sep 27, 2022 at 09:34:49 +0200, Amadeusz Sławiński wrote:
> On 9/26/2022 6:35 PM, Eugeniu Rosca wrote:
> >From: xiao jin <jin.xiao@...el.com>
> >
> >After start of fe and be, fe might go to close without triggering
> >STOP, and substream->runtime is freed. However, be is still at
> >START state and its substream->runtime still points to the
> >freed runtime.
> >
>
> Well if it is being freed, maybe pointer should be set to NULL instead in
> place that happens?
>
As soon as the agreement is reached that the patch is still
relevant/useful on the latest vanilla, I think this review
finding will receive proper attention.
Thanks,
Eugeniu
Powered by blists - more mailing lists