From: <nobuhiro1.iwamatsu@toshiba.co.jp> To: <xiujianfeng@huawei.com>, <mturquette@baylibre.com>, <sboyd@kernel.org> Cc: <linux-clk@vger.kernel.org>, <linux-arm-kernel@lists.infradead.org>, <linux-kernel@vger.kernel.org> Subject: RE: [PATCH] clk: visconti: Fix memory leak in visconti_register_pll() Date: Thu, 24 Nov 2022 01:22:28 +0000 [thread overview] Message-ID: <TYWPR01MB9420832555EFC60126BE0909920F9@TYWPR01MB9420.jpnprd01.prod.outlook.com> (raw) In-Reply-To: <20221122152353.204132-1-xiujianfeng@huawei.com> Hi Xiu, Thanks for your patch! > -----Original Message----- > From: Xiu Jianfeng <xiujianfeng@huawei.com> > Sent: Wednesday, November 23, 2022 12:24 AM > To: mturquette@baylibre.com; sboyd@kernel.org; iwamatsu nobuhiro(岩松 信 > 洋 □SWC◯ACT) <nobuhiro1.iwamatsu@toshiba.co.jp> > Cc: linux-clk@vger.kernel.org; linux-arm-kernel@lists.infradead.org; > linux-kernel@vger.kernel.org > Subject: [PATCH] clk: visconti: Fix memory leak in visconti_register_pll() > > @pll->rate_table has allocated memory by kmemdup(), if clk_hw_register() > fails, it should be freed, otherwise it will cause memory leak issue, this patch > fixes it. > > Fixes: b4cbe606dc36 ("clk: visconti: Add support common clock driver and > reset driver") > Signed-off-by: Xiu Jianfeng <xiujianfeng@huawei.com> Acked-by: Nobuhiro Iwamatsu <nobuhiro1.iwamatsu@toshiba.co.jp> Best regards, Nobuhiro > --- > drivers/clk/visconti/pll.c | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/drivers/clk/visconti/pll.c b/drivers/clk/visconti/pll.c index > a484cb945d67..1f3234f22667 100644 > --- a/drivers/clk/visconti/pll.c > +++ b/drivers/clk/visconti/pll.c > @@ -277,6 +277,7 @@ static struct clk_hw *visconti_register_pll(struct > visconti_pll_provider *ctx, > ret = clk_hw_register(NULL, &pll->hw); > if (ret) { > pr_err("failed to register pll clock %s : %d\n", name, ret); > + kfree(pll->rate_table); > kfree(pll); > pll_hw_clk = ERR_PTR(ret); > } > -- > 2.17.1 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: <nobuhiro1.iwamatsu@toshiba.co.jp> To: <xiujianfeng@huawei.com>, <mturquette@baylibre.com>, <sboyd@kernel.org> Cc: <linux-clk@vger.kernel.org>, <linux-arm-kernel@lists.infradead.org>, <linux-kernel@vger.kernel.org> Subject: RE: [PATCH] clk: visconti: Fix memory leak in visconti_register_pll() Date: Thu, 24 Nov 2022 01:22:28 +0000 [thread overview] Message-ID: <TYWPR01MB9420832555EFC60126BE0909920F9@TYWPR01MB9420.jpnprd01.prod.outlook.com> (raw) In-Reply-To: <20221122152353.204132-1-xiujianfeng@huawei.com> Hi Xiu, Thanks for your patch! > -----Original Message----- > From: Xiu Jianfeng <xiujianfeng@huawei.com> > Sent: Wednesday, November 23, 2022 12:24 AM > To: mturquette@baylibre.com; sboyd@kernel.org; iwamatsu nobuhiro(岩松 信 > 洋 □SWC◯ACT) <nobuhiro1.iwamatsu@toshiba.co.jp> > Cc: linux-clk@vger.kernel.org; linux-arm-kernel@lists.infradead.org; > linux-kernel@vger.kernel.org > Subject: [PATCH] clk: visconti: Fix memory leak in visconti_register_pll() > > @pll->rate_table has allocated memory by kmemdup(), if clk_hw_register() > fails, it should be freed, otherwise it will cause memory leak issue, this patch > fixes it. > > Fixes: b4cbe606dc36 ("clk: visconti: Add support common clock driver and > reset driver") > Signed-off-by: Xiu Jianfeng <xiujianfeng@huawei.com> Acked-by: Nobuhiro Iwamatsu <nobuhiro1.iwamatsu@toshiba.co.jp> Best regards, Nobuhiro > --- > drivers/clk/visconti/pll.c | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/drivers/clk/visconti/pll.c b/drivers/clk/visconti/pll.c index > a484cb945d67..1f3234f22667 100644 > --- a/drivers/clk/visconti/pll.c > +++ b/drivers/clk/visconti/pll.c > @@ -277,6 +277,7 @@ static struct clk_hw *visconti_register_pll(struct > visconti_pll_provider *ctx, > ret = clk_hw_register(NULL, &pll->hw); > if (ret) { > pr_err("failed to register pll clock %s : %d\n", name, ret); > + kfree(pll->rate_table); > kfree(pll); > pll_hw_clk = ERR_PTR(ret); > } > -- > 2.17.1
next prev parent reply other threads:[~2022-11-24 1:24 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-22 15:23 [PATCH] clk: visconti: Fix memory leak in visconti_register_pll() Xiu Jianfeng 2022-11-22 15:23 ` Xiu Jianfeng 2022-11-24 1:22 ` nobuhiro1.iwamatsu [this message] 2022-11-24 1:22 ` nobuhiro1.iwamatsu 2022-11-29 20:11 ` Stephen Boyd 2022-11-29 20:11 ` Stephen Boyd -- strict thread matches above, loose matches on Subject: below -- 2022-11-22 15:22 Xiu Jianfeng 2022-11-22 15:22 ` Xiu Jianfeng
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=TYWPR01MB9420832555EFC60126BE0909920F9@TYWPR01MB9420.jpnprd01.prod.outlook.com \ --to=nobuhiro1.iwamatsu@toshiba.co.jp \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-clk@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=mturquette@baylibre.com \ --cc=sboyd@kernel.org \ --cc=xiujianfeng@huawei.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.