From: Brian Masney <bmasney@redhat.com>
To: Louis-Alexis Eyraud <louisalexis.eyraud@collabora.com>
Cc: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Chen-Yu Tsai <wenst@chromium.org>,
Edward-JW Yang <edward-jw.yang@mediatek.com>,
Johnson Wang <johnson.wang@mediatek.com>,
kernel@collabora.com, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH] clk: mediatek: pllfh: Fix IO remapping leak in register_pllfhs error path
Date: Wed, 8 Jul 2026 12:50:41 -0400 [thread overview]
Message-ID: <ak5_4aTPwWPdczms@redhat.com> (raw)
In-Reply-To: <20260708-clk-mediatek-pllfh-fix-v1-1-2cfc2d6b258e@collabora.com>
Hi Louis-Alexis,
Thanks for the patch.
On Wed, Jul 08, 2026 at 11:18:59AM +0200, Louis-Alexis Eyraud wrote:
> When mtk_clk_register_pllfhs function fails to register a PLL, it
> unregisters all PLLs and cleans up itself in its error path before
> returning, so the function callers don't need to do it.
>
> But contrary to mtk_clk_unregister_pllfhs function, that does almost
> the same sequence, it does not free the IO memory mapped on fhctl node,
> leading to a leak.
>
> Fix this leak by factorizing the cleanup sequence in a new private
> function and use it both mtk_clk_register_pllfhs and
> mtk_clk_unregister_pllfhs functions.
>
> Also, change the loop index start value to avoid the -1 operation on
> index at each loop.
>
> Fixes: d7964de8a8ea ("clk: mediatek: Add new clock driver to handle FHCTL hardware")
> Signed-off-by: Louis-Alexis Eyraud <louisalexis.eyraud@collabora.com>
> ---
> This patch aims to fix a issue, detected by Sashiko
> during another series review ([1]), regarding the use of
> mtk_clk_register_pllfhs function.
>
> The patch is based on linux-next tree (tag: next-20260707).
>
> [1]: https://sashiko.dev/#/patchset/20260701-mt8189-clocks-system-base-v1-0-2b048feea50a%40collabora.com?part=6
> ---
> drivers/clk/mediatek/clk-pllfh.c | 87 ++++++++++++++++++----------------------
> 1 file changed, 39 insertions(+), 48 deletions(-)
>
> diff --git a/drivers/clk/mediatek/clk-pllfh.c b/drivers/clk/mediatek/clk-pllfh.c
> index aa95cd9197b3..7463aa35d7e3 100644
> --- a/drivers/clk/mediatek/clk-pllfh.c
> +++ b/drivers/clk/mediatek/clk-pllfh.c
> @@ -197,6 +197,43 @@ static void mtk_clk_unregister_pllfh(struct clk_hw *hw)
> kfree(fh);
> }
>
> +static void mtk_clk_cleanup_pllfhs(const struct mtk_pll_data *plls, int num_plls,
> + struct mtk_pllfh_data *pllfhs, int num_fhs,
> + struct clk_hw_onecell_data *clk_data)
> +{
> + void __iomem *base = NULL, *fhctl_base = NULL;
> + int i;
> +
> + for (i = num_plls - 1; i > 0; i--) {
It looks like this should be i >= 0
> + const struct mtk_pll_data *pll = &plls[i];
> + struct mtk_pllfh_data *pllfh;
> + bool use_fhctl;
> +
> + if (IS_ERR_OR_NULL(clk_data->hws[pll->id]))
> + continue;
> +
> + pllfh = get_pllfh_by_id(pllfhs, num_fhs, pll->id);
> + use_fhctl = fhctl_is_supported_and_enabled(pllfh);
> +
> + if (use_fhctl) {
> + fhctl_base = pllfh->state.base;
> + mtk_clk_unregister_pllfh(clk_data->hws[pll->id]);
> + } else {
> + base = mtk_clk_pll_get_base(clk_data->hws[pll->id],
> + pll);
> + mtk_clk_unregister_pll(clk_data->hws[pll->id]);
> + }
> +
> + clk_data->hws[pll->id] = ERR_PTR(-ENOENT);
> + }
> +
> + if (fhctl_base)
> + iounmap(fhctl_base);
> +
> + iounmap(base);
When use_fhctl is enabled for all PLLs, base will be NULL.
Brian
> +}
> +
> +
> int mtk_clk_register_pllfhs(struct device *dev,
> const struct mtk_pll_data *plls, int num_plls,
> struct mtk_pllfh_data *pllfhs, int num_fhs,
> @@ -238,24 +275,7 @@ int mtk_clk_register_pllfhs(struct device *dev,
> return 0;
>
> err:
> - while (--i >= 0) {
> - const struct mtk_pll_data *pll = &plls[i];
> - struct mtk_pllfh_data *pllfh;
> - bool use_fhctl;
> -
> - pllfh = get_pllfh_by_id(pllfhs, num_fhs, pll->id);
> - use_fhctl = fhctl_is_supported_and_enabled(pllfh);
> -
> - if (use_fhctl)
> - mtk_clk_unregister_pllfh(clk_data->hws[pll->id]);
> - else
> - mtk_clk_unregister_pll(clk_data->hws[pll->id]);
> -
> - clk_data->hws[pll->id] = ERR_PTR(-ENOENT);
> - }
> -
> - iounmap(base);
> -
> + mtk_clk_cleanup_pllfhs(plls, i, pllfhs, num_fhs, clk_data);
> return PTR_ERR(hw);
> }
> EXPORT_SYMBOL_GPL(mtk_clk_register_pllfhs);
> @@ -264,38 +284,9 @@ void mtk_clk_unregister_pllfhs(const struct mtk_pll_data *plls, int num_plls,
> struct mtk_pllfh_data *pllfhs, int num_fhs,
> struct clk_hw_onecell_data *clk_data)
> {
> - void __iomem *base = NULL, *fhctl_base = NULL;
> - int i;
> -
> if (!clk_data)
> return;
>
> - for (i = num_plls; i > 0; i--) {
> - const struct mtk_pll_data *pll = &plls[i - 1];
> - struct mtk_pllfh_data *pllfh;
> - bool use_fhctl;
> -
> - if (IS_ERR_OR_NULL(clk_data->hws[pll->id]))
> - continue;
> -
> - pllfh = get_pllfh_by_id(pllfhs, num_fhs, pll->id);
> - use_fhctl = fhctl_is_supported_and_enabled(pllfh);
> -
> - if (use_fhctl) {
> - fhctl_base = pllfh->state.base;
> - mtk_clk_unregister_pllfh(clk_data->hws[pll->id]);
> - } else {
> - base = mtk_clk_pll_get_base(clk_data->hws[pll->id],
> - pll);
> - mtk_clk_unregister_pll(clk_data->hws[pll->id]);
> - }
> -
> - clk_data->hws[pll->id] = ERR_PTR(-ENOENT);
> - }
> -
> - if (fhctl_base)
> - iounmap(fhctl_base);
> -
> - iounmap(base);
> + mtk_clk_cleanup_pllfhs(plls, num_plls, pllfhs, num_fhs, clk_data);
> }
> EXPORT_SYMBOL_GPL(mtk_clk_unregister_pllfhs);
>
> ---
> base-commit: b3a87fbe738f19cbe19411cf749f3d8c09c04de4
> change-id: 20260708-clk-mediatek-pllfh-fix-7e9ca35989e2
>
> Best regards,
> --
> Louis-Alexis Eyraud <louisalexis.eyraud@collabora.com>
>
prev parent reply other threads:[~2026-07-08 16:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 9:18 [PATCH] clk: mediatek: pllfh: Fix IO remapping leak in register_pllfhs error path Louis-Alexis Eyraud
2026-07-08 16:50 ` Brian Masney [this message]
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=ak5_4aTPwWPdczms@redhat.com \
--to=bmasney@redhat.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=edward-jw.yang@mediatek.com \
--cc=johnson.wang@mediatek.com \
--cc=kernel@collabora.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=louisalexis.eyraud@collabora.com \
--cc=matthias.bgg@gmail.com \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
--cc=wenst@chromium.org \
/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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox