From: Conor Dooley <conor@kernel.org>
To: Jiasheng Jiang <jiasheng@iscas.ac.cn>,
mturquette@baylibre.com, sboyd@kernel.org,
claudiu.beznea@microchip.com, conor.dooley@microchip.com
Cc: linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clk: microchip: Add check for devm_kzalloc
Date: Thu, 08 Dec 2022 09:11:16 +0100 [thread overview]
Message-ID: <F2FCAF36-B78B-4233-B0DE-A5AAE73EBCC5@kernel.org> (raw)
In-Reply-To: <20221208074025.29015-1-jiasheng@iscas.ac.cn>
On 8 December 2022 08:40:25 GMT+01:00, Jiasheng Jiang <jiasheng@iscas.ac.cn> wrote:
>As devm_kzalloc may return NULL pointer, the return value should
>be checked and return error if it fails since NULL is a invalid
>value of "name" .
>
>Fixes: d39fb172760e ("clk: microchip: add PolarFire SoC fabric clock support")
>Signed-off-by: Jiasheng Jiang <jiasheng@iscas.ac.cn>
Someone already sent this patch, but thanks.
>---
> drivers/clk/microchip/clk-mpfs-ccc.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
>diff --git a/drivers/clk/microchip/clk-mpfs-ccc.c b/drivers/clk/microchip/clk-mpfs-ccc.c
>index 7be028dced63..32aae880a14f 100644
>--- a/drivers/clk/microchip/clk-mpfs-ccc.c
>+++ b/drivers/clk/microchip/clk-mpfs-ccc.c
>@@ -166,6 +166,9 @@ static int mpfs_ccc_register_outputs(struct device *dev, struct mpfs_ccc_out_hw_
> struct mpfs_ccc_out_hw_clock *out_hw = &out_hws[i];
> char *name = devm_kzalloc(dev, 23, GFP_KERNEL);
>
>+ if (!name)
>+ return -ENOMEM;
>+
> snprintf(name, 23, "%s_out%u", parent->name, i);
> out_hw->divider.hw.init = CLK_HW_INIT_HW(name, &parent->hw, &clk_divider_ops, 0);
> out_hw->divider.reg = data->pll_base[i / MPFS_CCC_OUTPUTS_PER_PLL] +
>@@ -200,6 +203,9 @@ static int mpfs_ccc_register_plls(struct device *dev, struct mpfs_ccc_pll_hw_clo
> struct mpfs_ccc_pll_hw_clock *pll_hw = &pll_hws[i];
> char *name = devm_kzalloc(dev, 18, GFP_KERNEL);
>
>+ if (!name)
>+ return -ENOMEM;
>+
> pll_hw->base = data->pll_base[i];
> snprintf(name, 18, "ccc%s_pll%u", strchrnul(dev->of_node->full_name, '@'), i);
> pll_hw->name = (const char *)name;
prev parent reply other threads:[~2022-12-08 8:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-08 7:40 Jiasheng Jiang
2022-12-08 8:11 ` Conor Dooley [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=F2FCAF36-B78B-4233-B0DE-A5AAE73EBCC5@kernel.org \
--to=conor@kernel.org \
--cc=claudiu.beznea@microchip.com \
--cc=conor.dooley@microchip.com \
--cc=jiasheng@iscas.ac.cn \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@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®