[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230203170121.187108bd@booty>
Date: Fri, 3 Feb 2023 17:01:21 +0100
From: Luca Ceresoli <luca.ceresoli@...tlin.com>
To: Johan Hovold <johan+linaro@...nel.org>
Cc: Georgi Djakov <djakov@...nel.org>, Shawn Guo <shawnguo@...nel.org>,
Sascha Hauer <s.hauer@...gutronix.de>,
Pengutronix Kernel Team <kernel@...gutronix.de>,
Fabio Estevam <festevam@...il.com>,
NXP Linux Team <linux-imx@....com>,
Andy Gross <agross@...nel.org>,
Bjorn Andersson <andersson@...nel.org>,
Konrad Dybcio <konrad.dybcio@...aro.org>,
Sylwester Nawrocki <s.nawrocki@...sung.com>,
Artur Świgoń <a.swigon@...sung.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
Alim Akhtar <alim.akhtar@...sung.com>,
Thierry Reding <thierry.reding@...il.com>,
Jonathan Hunter <jonathanh@...dia.com>,
linux-pm@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-arm-msm@...r.kernel.org, linux-samsung-soc@...r.kernel.org,
linux-tegra@...r.kernel.org, linux-kernel@...r.kernel.org,
stable@...r.kernel.org, Leonard Crestez <leonard.crestez@....com>,
Alexandre Bailon <abailon@...libre.com>
Subject: Re: [PATCH 04/23] interconnect: imx: fix registration race
Hello Johan,
On Wed, 1 Feb 2023 11:15:40 +0100
Johan Hovold <johan+linaro@...nel.org> wrote:
> The current interconnect provider registration interface is inherently
> racy as nodes are not added until the after adding the provider. This
> can specifically cause racing DT lookups to fail.
>
> Switch to using the new API where the provider is not registered until
> after it has been fully initialised.
>
> Fixes: f0d8048525d7 ("interconnect: Add imx core driver")
> Cc: stable@...r.kernel.org # 5.8
> Cc: Leonard Crestez <leonard.crestez@....com>
> Cc: Alexandre Bailon <abailon@...libre.com>
> Signed-off-by: Johan Hovold <johan+linaro@...nel.org>
Georgi pointed me to this series after I reported a bug yesterday [0],
that I found on iMX8MP. So I ran some tests with my original, failing
tree, minus one patch with my debugging code to hunt for the bug, plus
patches 1-4 of this series.
The original code was failing approx 5~10% of the times. With your 4
patches applied it ran 139 times with zero errors, which looks great! I
won't be able to do more testing until next Monday to be extra sure.
[0]
https://lore.kernel.org/linux-arm-kernel/20230202175525.3dba79a7@booty/T/#u
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
Powered by blists - more mailing lists