From: Konrad Dybcio <konrad.dybcio@linaro.org> To: Johan Hovold <johan+linaro@kernel.org>, Georgi Djakov <djakov@kernel.org> Cc: "Shawn Guo" <shawnguo@kernel.org>, "Sascha Hauer" <s.hauer@pengutronix.de>, "Pengutronix Kernel Team" <kernel@pengutronix.de>, "Fabio Estevam" <festevam@gmail.com>, "NXP Linux Team" <linux-imx@nxp.com>, "Andy Gross" <agross@kernel.org>, "Bjorn Andersson" <andersson@kernel.org>, "Sylwester Nawrocki" <s.nawrocki@samsung.com>, "Artur Świgoń" <a.swigon@samsung.com>, "Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>, "Alim Akhtar" <alim.akhtar@samsung.com>, "Thierry Reding" <thierry.reding@gmail.com>, "Jonathan Hunter" <jonathanh@nvidia.com>, linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-arm-msm@vger.kernel.org, linux-samsung-soc@vger.kernel.org, linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org, stable@vger.kernel.org Subject: Re: [PATCH 02/23] interconnect: fix icc_provider_del() error handling Date: Wed, 1 Feb 2023 12:16:50 +0100 [thread overview] Message-ID: <9b7813d0-ec4e-a4a1-168f-de0797bcdf64@linaro.org> (raw) In-Reply-To: <20230201101559.15529-3-johan+linaro@kernel.org> On 1.02.2023 11:15, Johan Hovold wrote: > The interconnect framework currently expects that providers are only > removed when there are no users and after all nodes have been removed. > > There is currently nothing that guarantees this to be the case and the > framework does not do any reference counting, but refusing to remove the > provider is never correct as that would leave a dangling pointer to a > resource that is about to be released in the global provider list (e.g. > accessible through debugfs). > > Replace the current sanity checks with WARN_ON() so that the provider is > always removed. I spent a considerable amount of time scratching my head what WARN_ON has to do with removing list items.. I suppose "don't return early and replace pr_warn with WARN_ON" would have been clearer, but maybe that's just me in the morning.. > > Fixes: 11f1ceca7031 ("interconnect: Add generic on-chip interconnect API") > Cc: stable@vger.kernel.org # 5.1: 680f8666baf6: interconnect: Make icc_provider_del() return void > Signed-off-by: Johan Hovold <johan+linaro@kernel.org> > --- Reviewed-by: Konrad Dybcio <konrad.dybcio@linaro.org> Konrad > drivers/interconnect/core.c | 14 ++------------ > 1 file changed, 2 insertions(+), 12 deletions(-) > > diff --git a/drivers/interconnect/core.c b/drivers/interconnect/core.c > index dc61620a0191..43c5c8503ee8 100644 > --- a/drivers/interconnect/core.c > +++ b/drivers/interconnect/core.c > @@ -1062,18 +1062,8 @@ EXPORT_SYMBOL_GPL(icc_provider_add); > void icc_provider_del(struct icc_provider *provider) > { > mutex_lock(&icc_lock); > - if (provider->users) { > - pr_warn("interconnect provider still has %d users\n", > - provider->users); > - mutex_unlock(&icc_lock); > - return; > - } > - > - if (!list_empty(&provider->nodes)) { > - pr_warn("interconnect provider still has nodes\n"); > - mutex_unlock(&icc_lock); > - return; > - } > + WARN_ON(provider->users); > + WARN_ON(!list_empty(&provider->nodes)); > > list_del(&provider->provider_list); > mutex_unlock(&icc_lock);
WARNING: multiple messages have this Message-ID (diff)
From: Konrad Dybcio <konrad.dybcio@linaro.org> To: Johan Hovold <johan+linaro@kernel.org>, Georgi Djakov <djakov@kernel.org> Cc: "Shawn Guo" <shawnguo@kernel.org>, "Sascha Hauer" <s.hauer@pengutronix.de>, "Pengutronix Kernel Team" <kernel@pengutronix.de>, "Fabio Estevam" <festevam@gmail.com>, "NXP Linux Team" <linux-imx@nxp.com>, "Andy Gross" <agross@kernel.org>, "Bjorn Andersson" <andersson@kernel.org>, "Sylwester Nawrocki" <s.nawrocki@samsung.com>, "Artur Świgoń" <a.swigon@samsung.com>, "Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>, "Alim Akhtar" <alim.akhtar@samsung.com>, "Thierry Reding" <thierry.reding@gmail.com>, "Jonathan Hunter" <jonathanh@nvidia.com>, linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-arm-msm@vger.kernel.org, linux-samsung-soc@vger.kernel.org, linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org, stable@vger.kernel.org Subject: Re: [PATCH 02/23] interconnect: fix icc_provider_del() error handling Date: Wed, 1 Feb 2023 12:16:50 +0100 [thread overview] Message-ID: <9b7813d0-ec4e-a4a1-168f-de0797bcdf64@linaro.org> (raw) In-Reply-To: <20230201101559.15529-3-johan+linaro@kernel.org> On 1.02.2023 11:15, Johan Hovold wrote: > The interconnect framework currently expects that providers are only > removed when there are no users and after all nodes have been removed. > > There is currently nothing that guarantees this to be the case and the > framework does not do any reference counting, but refusing to remove the > provider is never correct as that would leave a dangling pointer to a > resource that is about to be released in the global provider list (e.g. > accessible through debugfs). > > Replace the current sanity checks with WARN_ON() so that the provider is > always removed. I spent a considerable amount of time scratching my head what WARN_ON has to do with removing list items.. I suppose "don't return early and replace pr_warn with WARN_ON" would have been clearer, but maybe that's just me in the morning.. > > Fixes: 11f1ceca7031 ("interconnect: Add generic on-chip interconnect API") > Cc: stable@vger.kernel.org # 5.1: 680f8666baf6: interconnect: Make icc_provider_del() return void > Signed-off-by: Johan Hovold <johan+linaro@kernel.org> > --- Reviewed-by: Konrad Dybcio <konrad.dybcio@linaro.org> Konrad > drivers/interconnect/core.c | 14 ++------------ > 1 file changed, 2 insertions(+), 12 deletions(-) > > diff --git a/drivers/interconnect/core.c b/drivers/interconnect/core.c > index dc61620a0191..43c5c8503ee8 100644 > --- a/drivers/interconnect/core.c > +++ b/drivers/interconnect/core.c > @@ -1062,18 +1062,8 @@ EXPORT_SYMBOL_GPL(icc_provider_add); > void icc_provider_del(struct icc_provider *provider) > { > mutex_lock(&icc_lock); > - if (provider->users) { > - pr_warn("interconnect provider still has %d users\n", > - provider->users); > - mutex_unlock(&icc_lock); > - return; > - } > - > - if (!list_empty(&provider->nodes)) { > - pr_warn("interconnect provider still has nodes\n"); > - mutex_unlock(&icc_lock); > - return; > - } > + WARN_ON(provider->users); > + WARN_ON(!list_empty(&provider->nodes)); > > list_del(&provider->provider_list); > mutex_unlock(&icc_lock); _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-02-01 11:17 UTC|newest] Thread overview: 118+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-01 10:15 [PATCH 00/23] interconnect: fix racy provider registration Johan Hovold 2023-02-01 10:15 ` Johan Hovold 2023-02-01 10:15 ` [PATCH 01/23] interconnect: fix mem leak when freeing nodes Johan Hovold 2023-02-01 10:15 ` Johan Hovold 2023-02-01 11:18 ` Konrad Dybcio 2023-02-01 11:18 ` Konrad Dybcio 2023-02-01 10:15 ` [PATCH 02/23] interconnect: fix icc_provider_del() error handling Johan Hovold 2023-02-01 10:15 ` Johan Hovold 2023-02-01 11:16 ` Konrad Dybcio [this message] 2023-02-01 11:16 ` Konrad Dybcio 2023-02-01 10:15 ` [PATCH 03/23] interconnect: fix provider registration API Johan Hovold 2023-02-01 10:15 ` Johan Hovold 2023-02-03 2:48 ` Konrad Dybcio 2023-02-03 2:48 ` Konrad Dybcio 2023-02-01 10:15 ` [PATCH 04/23] interconnect: imx: fix registration race Johan Hovold 2023-02-01 10:15 ` Johan Hovold 2023-02-03 2:49 ` Konrad Dybcio 2023-02-03 2:49 ` Konrad Dybcio 2023-02-03 16:01 ` Luca Ceresoli 2023-02-03 16:01 ` Luca Ceresoli 2023-02-06 8:09 ` Johan Hovold 2023-02-06 8:09 ` Johan Hovold 2023-02-06 20:52 ` Luca Ceresoli 2023-02-06 20:52 ` Luca Ceresoli 2023-02-01 10:15 ` [PATCH 05/23] interconnect: qcom: osm-l3: " Johan Hovold 2023-02-01 10:15 ` Johan Hovold 2023-02-03 2:51 ` Konrad Dybcio 2023-02-03 2:51 ` Konrad Dybcio 2023-02-01 10:15 ` [PATCH 06/23] interconnect: qcom: rpm: fix probe child-node error handling Johan Hovold 2023-02-01 10:15 ` Johan Hovold 2023-02-03 2:52 ` Konrad Dybcio 2023-02-03 2:52 ` Konrad Dybcio 2023-02-01 10:15 ` [PATCH 07/23] interconnect: qcom: rpm: fix probe PM domain " Johan Hovold 2023-02-01 10:15 ` Johan Hovold 2023-02-03 2:53 ` Konrad Dybcio 2023-02-03 2:53 ` Konrad Dybcio 2023-03-11 18:17 ` Christophe JAILLET 2023-03-11 18:17 ` Christophe JAILLET 2023-03-13 8:18 ` Johan Hovold 2023-03-13 8:18 ` Johan Hovold 2023-02-01 10:15 ` [PATCH 08/23] interconnect: qcom: rpm: fix registration race Johan Hovold 2023-02-01 10:15 ` Johan Hovold 2023-02-03 2:53 ` Konrad Dybcio 2023-02-03 2:53 ` Konrad Dybcio 2023-02-03 4:06 ` Jun Nie 2023-02-03 4:06 ` Jun Nie 2023-02-01 10:15 ` [PATCH 09/23] interconnect: qcom: rpmh: fix probe child-node error handling Johan Hovold 2023-02-01 10:15 ` Johan Hovold 2023-02-03 2:54 ` Konrad Dybcio 2023-02-03 2:54 ` Konrad Dybcio 2023-02-01 10:15 ` [PATCH 10/23] interconnect: qcom: rpmh: fix registration race Johan Hovold 2023-02-01 10:15 ` Johan Hovold 2023-02-03 2:55 ` Konrad Dybcio 2023-02-03 2:55 ` Konrad Dybcio 2023-02-01 10:15 ` [PATCH 11/23] interconnect: qcom: msm8974: " Johan Hovold 2023-02-01 10:15 ` Johan Hovold 2023-02-02 23:13 ` Brian Masney 2023-02-02 23:13 ` Brian Masney 2023-02-03 2:56 ` Konrad Dybcio 2023-02-03 2:56 ` Konrad Dybcio 2023-02-01 10:15 ` [PATCH 12/23] interconnect: qcom: sm8450: " Johan Hovold 2023-02-01 10:15 ` Johan Hovold 2023-02-03 2:56 ` Konrad Dybcio 2023-02-03 2:56 ` Konrad Dybcio 2023-02-06 12:10 ` Vinod Koul 2023-02-06 12:10 ` Vinod Koul 2023-02-01 10:15 ` [PATCH 13/23] interconnect: qcom: sm8550: " Johan Hovold 2023-02-01 10:15 ` Johan Hovold 2023-02-01 10:20 ` Abel Vesa 2023-02-01 10:20 ` Abel Vesa 2023-02-03 2:57 ` Konrad Dybcio 2023-02-03 2:57 ` Konrad Dybcio 2023-02-01 10:15 ` [PATCH 14/23] interconnect: exynos: fix node leak in probe PM QoS error path Johan Hovold 2023-02-01 10:15 ` Johan Hovold 2023-02-02 10:58 ` Krzysztof Kozlowski 2023-02-02 10:58 ` Krzysztof Kozlowski 2023-02-01 10:15 ` [PATCH 15/23] interconnect: exynos: fix registration race Johan Hovold 2023-02-01 10:15 ` Johan Hovold 2023-02-02 11:04 ` Krzysztof Kozlowski 2023-02-02 11:04 ` Krzysztof Kozlowski 2023-02-02 12:17 ` Johan Hovold 2023-02-02 12:17 ` Johan Hovold 2023-02-02 12:20 ` Krzysztof Kozlowski 2023-02-02 12:20 ` Krzysztof Kozlowski 2023-02-01 10:15 ` [PATCH 16/23] interconnect: exynos: drop redundant link destroy Johan Hovold 2023-02-01 10:15 ` Johan Hovold 2023-02-02 11:09 ` Krzysztof Kozlowski 2023-02-02 11:09 ` Krzysztof Kozlowski 2023-02-01 10:15 ` [PATCH 17/23] memory: tegra: fix interconnect registration race Johan Hovold 2023-02-01 10:15 ` Johan Hovold 2023-02-02 12:21 ` Krzysztof Kozlowski 2023-02-02 12:21 ` Krzysztof Kozlowski 2023-02-01 10:15 ` [PATCH 18/23] memory: tegra124-emc: " Johan Hovold 2023-02-01 10:15 ` Johan Hovold 2023-02-02 12:21 ` Krzysztof Kozlowski 2023-02-02 12:21 ` Krzysztof Kozlowski 2023-02-01 10:15 ` [PATCH 19/23] memory: tegra20-emc: " Johan Hovold 2023-02-01 10:15 ` Johan Hovold 2023-02-02 12:21 ` Krzysztof Kozlowski 2023-02-02 12:21 ` Krzysztof Kozlowski 2023-02-01 10:15 ` [PATCH 20/23] memory: tegra30-emc: " Johan Hovold 2023-02-01 10:15 ` Johan Hovold 2023-02-02 12:21 ` Krzysztof Kozlowski 2023-02-02 12:21 ` Krzysztof Kozlowski 2023-02-01 10:15 ` [PATCH 21/23] interconnect: drop racy registration API Johan Hovold 2023-02-01 10:15 ` Johan Hovold 2023-02-03 2:58 ` Konrad Dybcio 2023-02-03 2:58 ` Konrad Dybcio 2023-02-01 10:15 ` [PATCH 22/23] interconnect: drop unused icc_get() interface Johan Hovold 2023-02-01 10:15 ` Johan Hovold 2023-02-03 2:59 ` Konrad Dybcio 2023-02-03 2:59 ` Konrad Dybcio 2023-02-01 10:15 ` [PATCH 23/23] interconnect: drop unused icc_link_destroy() interface Johan Hovold 2023-02-01 10:15 ` Johan Hovold 2023-02-02 11:13 ` [PATCH 00/23] interconnect: fix racy provider registration Krzysztof Kozlowski 2023-02-02 11:13 ` Krzysztof Kozlowski 2023-02-02 12:20 ` Johan Hovold 2023-02-02 12:20 ` Johan Hovold
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=9b7813d0-ec4e-a4a1-168f-de0797bcdf64@linaro.org \ --to=konrad.dybcio@linaro.org \ --cc=a.swigon@samsung.com \ --cc=agross@kernel.org \ --cc=alim.akhtar@samsung.com \ --cc=andersson@kernel.org \ --cc=djakov@kernel.org \ --cc=festevam@gmail.com \ --cc=johan+linaro@kernel.org \ --cc=jonathanh@nvidia.com \ --cc=kernel@pengutronix.de \ --cc=krzysztof.kozlowski@linaro.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-arm-msm@vger.kernel.org \ --cc=linux-imx@nxp.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-pm@vger.kernel.org \ --cc=linux-samsung-soc@vger.kernel.org \ --cc=linux-tegra@vger.kernel.org \ --cc=s.hauer@pengutronix.de \ --cc=s.nawrocki@samsung.com \ --cc=shawnguo@kernel.org \ --cc=stable@vger.kernel.org \ --cc=thierry.reding@gmail.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: linkBe 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.