From: Peng Fan <peng.fan@oss.nxp.com>
To: Yuxing Liu <lyx2022@hust.edu.cn>, Abel Vesa <abelvesa@kernel.org>,
Peng Fan <peng.fan@nxp.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, 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>,
Anson Huang <Anson.Huang@nxp.com>
Cc: hust-os-kernel-patches@googlegroups.com,
Dongliang Mu <dzm91@hust.edu.cn>,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] clk: imx: clk-imx8mp: use dev_ managed memory to avoid memory leak in imx8mp_clocks_probe()
Date: Fri, 28 Apr 2023 15:53:44 +0800 [thread overview]
Message-ID: <e336d1d4-74e9-282b-1b80-e5f5617fab06@oss.nxp.com> (raw)
In-Reply-To: <20230424092346.124509-1-lyx2022@hust.edu.cn>
On 4/24/2023 5:23 PM, Yuxing Liu wrote:
> Replace of_iomap() and kzalloc() with devm_of_iomap() and devm_kzalloc()
> which can automatically release the related memory when the device
> or driver is disassembled or unloaded to avoid potential memory leak.
What do you mean "disassembled"? The i.MX8MP is an SoC which has Clock
IP built in the device.
Regards,
Peng.
>
> In this case,iounmap(anatop_base) in line 427,433 are removed
> as manual release is not required.
>
> Fixes: 9c140d992676 ("clk: imx: Add support for i.MX8MP clock driver")
> Signed-off-by: Yuxing Liu <lyx2022@hust.edu.cn>
> Reviewed-by: Dongliang Mu <dzm91@hust.edu.cn>
> ---
> This issue is found by static analysis and remains untested.
> ---
> drivers/clk/imx/clk-imx8mp.c | 16 ++++++----------
> 1 file changed, 6 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/clk/imx/clk-imx8mp.c b/drivers/clk/imx/clk-imx8mp.c
> index 3253589851ff..353d58b665f9 100644
> --- a/drivers/clk/imx/clk-imx8mp.c
> +++ b/drivers/clk/imx/clk-imx8mp.c
> @@ -416,23 +416,19 @@ static int imx8mp_clocks_probe(struct platform_device *pdev)
> void __iomem *anatop_base, *ccm_base;
>
> np = of_find_compatible_node(NULL, NULL, "fsl,imx8mp-anatop");
> - anatop_base = of_iomap(np, 0);
> + anatop_base = devm_of_iomap(dev, np, 0, NULL);
> of_node_put(np);
> - if (WARN_ON(!anatop_base))
> - return -ENOMEM;
> + if (WARN_ON(IS_ERR(anatop_base)))
> + return PTR_ERR(anatop_base);
>
> np = dev->of_node;
> ccm_base = devm_platform_ioremap_resource(pdev, 0);
> - if (WARN_ON(IS_ERR(ccm_base))) {
> - iounmap(anatop_base);
> + if (WARN_ON(IS_ERR(ccm_base)))
> return PTR_ERR(ccm_base);
> - }
>
> - clk_hw_data = kzalloc(struct_size(clk_hw_data, hws, IMX8MP_CLK_END), GFP_KERNEL);
> - if (WARN_ON(!clk_hw_data)) {
> - iounmap(anatop_base);
> + clk_hw_data = devm_kzalloc(dev, struct_size(clk_hw_data, hws, IMX8MP_CLK_END), GFP_KERNEL);
> + if (WARN_ON(!clk_hw_data))
> return -ENOMEM;
> - }
>
> clk_hw_data->num = IMX8MP_CLK_END;
> hws = clk_hw_data->hws;
prev parent reply other threads:[~2023-04-28 7:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 9:23 Yuxing Liu
2023-04-28 7:53 ` Peng Fan [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=e336d1d4-74e9-282b-1b80-e5f5617fab06@oss.nxp.com \
--to=peng.fan@oss.nxp.com \
--cc=Anson.Huang@nxp.com \
--cc=abelvesa@kernel.org \
--cc=dzm91@hust.edu.cn \
--cc=festevam@gmail.com \
--cc=hust-os-kernel-patches@googlegroups.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lyx2022@hust.edu.cn \
--cc=mturquette@baylibre.com \
--cc=peng.fan@nxp.com \
--cc=s.hauer@pengutronix.de \
--cc=sboyd@kernel.org \
--cc=shawnguo@kernel.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
all inboxes | Powered by JetHome®