From: <Claudiu.Beznea@microchip.com>
To: <conor@kernel.org>, <tanghui20@huawei.com>
Cc: <mturquette@baylibre.com>, <sboyd@kernel.org>,
<linux-clk@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<yusongping@huawei.com>, <Conor.Dooley@microchip.com>
Subject: Re: [PATCH] clk: microchip: check for null return of devm_kzalloc()
Date: Fri, 25 Nov 2022 13:48:48 +0000 [thread overview]
Message-ID: <666f8502-86dd-b000-92d2-ec3fd90e332d@microchip.com> (raw)
In-Reply-To: <Y3izOuF56/NywpOR@spud>
On 19.11.2022 12:43, Conor Dooley wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> On Sat, Nov 19, 2022 at 01:48:58PM +0800, Hui Tang wrote:
>> Because of the possilble failure of devm_kzalloc(), name might be NULL and
>> will cause null pointer derefrence later.
>
> In theory, yeah?
>
> (note to self, s/refrence/reference/, s/possilble/possible)
Applied to clk-microchip-fixes with these adjustments, thanks!
>
>> Therefore, it might be better to check it and directly return -ENOMEM.
>
> I agree with your use of might here. If the allocations do fail, we
> likely aren't getting the system off the ground anyway - but there is
> no harm in checking.
>
> Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
>
> @Claudiu, supposedly I can push to the at91 repo now so I will try to do
> that.
>
> Thanks,
> Conor.
>
>>
>> Fixes: d39fb172760e ("clk: microchip: add PolarFire SoC fabric clock support")
>> Signed-off-by: Hui Tang <tanghui20@huawei.com>
>> ---
>> 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;
>> --
>> 2.17.1
>>
prev parent reply other threads:[~2022-11-25 13:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-19 5:48 [PATCH] clk: microchip: check for null return of devm_kzalloc() Hui Tang
2022-11-19 10:43 ` Conor Dooley
2022-11-21 7:26 ` Hui Tang
2022-11-25 13:48 ` Claudiu.Beznea [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=666f8502-86dd-b000-92d2-ec3fd90e332d@microchip.com \
--to=claudiu.beznea@microchip.com \
--cc=Conor.Dooley@microchip.com \
--cc=conor@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
--cc=tanghui20@huawei.com \
--cc=yusongping@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: 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