From: Thierry Reding <thierry.reding@kernel.org>
To: Jerome Brunet <jbrunet@baylibre.com>
Cc: Rosen Penev <rosenp@gmail.com>,
linux-clk@vger.kernel.org,
Prashant Gaikwad <pgaikwad@nvidia.com>,
Stephen Boyd <sboyd@kernel.org>,
Brian Masney <bmasney+clk@redhat.com>,
Jerome Brunet <jbrunet+clk@baylibre.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Kees Cook <kees@kernel.org>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
"open list:TEGRA ARCHITECTURE SUPPORT"
<linux-tegra@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
"open list:KERNEL HARDENING (not covered by other
areas):Keyword:b__counted_by(_le|_be|_ptr)?b"
<linux-hardening@vger.kernel.org>
Subject: Re: [PATCH RESEND] clk: tegra: bmp: remove kcalloc
Date: Wed, 30 Sep 2026 11:29:16 +0200 [thread overview]
Message-ID: <arzWBhCQCCUBI95M@orome> (raw)
In-Reply-To: <1jwls32msl.fsf@starbuckisacylon.baylibre.com>
[-- Attachment #1: Type: text/plain, Size: 1965 bytes --]
On Wed, Sep 30, 2026 at 09:58:18AM +0200, Jerome Brunet wrote:
> On mar. 29 sept. 2026 at 12:24, Rosen Penev <rosenp@gmail.com> wrote:
>
> > Use a flexible array member to avoid allocating separately.
> >
> > Use __counted_by for extra runtime analysis.
> >
> > Signed-off-by: Rosen Penev <rosenp@gmail.com>
> > ---
> > drivers/clk/tegra/clk-bpmp.c | 12 +++---------
> > 1 file changed, 3 insertions(+), 9 deletions(-)
> >
> > diff --git a/drivers/clk/tegra/clk-bpmp.c b/drivers/clk/tegra/clk-bpmp.c
> > index 067a8555c4e7..15b976162b59 100644
> > --- a/drivers/clk/tegra/clk-bpmp.c
> > +++ b/drivers/clk/tegra/clk-bpmp.c
> > @@ -32,7 +32,7 @@ struct tegra_bpmp_clk {
> > unsigned int id;
> >
> > unsigned int num_parents;
> > - unsigned int *parents;
> > + unsigned int parents[] __counted_by(num_parents);
> > };
> >
> > static inline struct tegra_bpmp_clk *to_tegra_bpmp_clk(struct clk_hw *hw)
> > @@ -518,20 +518,14 @@ tegra_bpmp_clk_register(struct tegra_bpmp *bpmp,
> > unsigned int i;
> > int err;
> >
> > - clk = devm_kzalloc(bpmp->dev, sizeof(*clk), GFP_KERNEL);
> > + clk = devm_kzalloc(bpmp->dev, struct_size(clk, parents, info->num_parents), GFP_KERNEL);
> > if (!clk)
> > return ERR_PTR(-ENOMEM);
> >
> > + clk->num_parents = info->num_parents;
> > clk->id = info->id;
> > clk->bpmp = bpmp;
> >
> > - clk->parents = devm_kcalloc(bpmp->dev, info->num_parents,
> > - sizeof(*clk->parents), GFP_KERNEL);
> > - if (!clk->parents)
> > - return ERR_PTR(-ENOMEM);
> > -
> > - clk->num_parents = info->num_parents;
> > -
>
> What is the benefit of doing this ? It looks like you are just trading
> one alloc for another here ?
I think the point is allocating the parents array as part of the main
allocation, so we end up with one allocation instead of two. This avoids
fragmentation and overhead and is possibly a little bit faster.
Seems fine to me.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-09-30 9:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 19:24 Rosen Penev
2026-09-30 7:58 ` Jerome Brunet
2026-09-30 9:29 ` Thierry Reding [this message]
2026-09-30 9:33 ` Thierry Reding
2026-09-30 11:06 ` Jon Hunter
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=arzWBhCQCCUBI95M@orome \
--to=thierry.reding@kernel.org \
--cc=bmasney+clk@redhat.com \
--cc=gustavoars@kernel.org \
--cc=jbrunet+clk@baylibre.com \
--cc=jbrunet@baylibre.com \
--cc=jonathanh@nvidia.com \
--cc=kees@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=pgaikwad@nvidia.com \
--cc=rosenp@gmail.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®