From: Stephen Boyd <sboyd@kernel.org>
To: "Conor Dooley" <conor.dooley@microchip.com>,
"Dinh Nguyen" <dinguyen@kernel.org>,
"Erick Archer" <erick.archer@gmx.com>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
"Heiko Stuebner" <heiko@sntech.de>,
"Michael Turquette" <mturquette@baylibre.com>,
"Nick Alcock" <nick.alcock@oracle.com>,
"Rob Herring" <robh@kernel.org>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Erick Archer <erick.archer@gmx.com>,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-hardening@vger.kernel.org
Subject: Re: [PATCH] clk: hisilicon: Use devm_kcalloc() instead of devm_kzalloc()
Date: Wed, 21 Feb 2024 20:27:32 -0800 [thread overview]
Message-ID: <61113ffd54a32399ebdc31fc1a57912f.sboyd@kernel.org> (raw)
In-Reply-To: <20240121142946.2796-1-erick.archer@gmx.com>
Quoting Erick Archer (2024-01-21 06:29:46)
> As noted in the "Deprecated Interfaces, Language Features, Attributes,
> and Conventions" documentation [1], size calculations (especially
> multiplication) should not be performed in memory allocator (or similar)
> function arguments due to the risk of them overflowing. This could lead
> to values wrapping around and a smaller allocation being made than the
> caller was expecting. Using those allocations could lead to linear
> overflows of heap memory and other misbehaviors.
>
> So, use the purpose specific devm_kcalloc() function instead of the
> argument size * count in the devm_kzalloc() function.
>
> Link: https://www.kernel.org/doc/html/next/process/deprecated.html#open-coded-arithmetic-in-allocator-arguments [1]
> Link: https://github.com/KSPP/linux/issues/162
> Signed-off-by: Erick Archer <erick.archer@gmx.com>
> ---
Applied to clk-next
prev parent reply other threads:[~2024-02-22 4:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-21 14:29 [PATCH] clk: hisilicon: Use devm_kcalloc() instead of devm_kzalloc() Erick Archer
2024-01-22 6:56 ` Uwe Kleine-König
2024-01-22 17:51 ` Gustavo A. R. Silva
2024-02-22 4:27 ` Stephen Boyd [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=61113ffd54a32399ebdc31fc1a57912f.sboyd@kernel.org \
--to=sboyd@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=dinguyen@kernel.org \
--cc=erick.archer@gmx.com \
--cc=gustavoars@kernel.org \
--cc=heiko@sntech.de \
--cc=linux-clk@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=nick.alcock@oracle.com \
--cc=robh@kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
/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