From: Brian Masney <bmasney@redhat.com>
To: Rosen Penev <rosenp@gmail.com>
Cc: linux-clk@vger.kernel.org, Andrew Lunn <andrew@lunn.ch>,
Gregory Clement <gregory.clement@bootlin.com>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Kees Cook <kees@kernel.org>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
"moderated list:ARM/Marvell Kirkwood and Armada 370, 375,
38x,..." <linux-arm-kernel@lists.infradead.org>,
open list <linux-kernel@vger.kernel.org>,
"open list:KERNEL HARDENING (not covered by other
areas):Keyword:b__counted_by(_le|_be)?b"
<linux-hardening@vger.kernel.org>
Subject: Re: [PATCH] clk: mvebu: use kzalloc_flex
Date: Fri, 3 Apr 2026 09:29:26 -0400 [thread overview]
Message-ID: <ac_AtoG1j_I2m9Ja@redhat.com> (raw)
In-Reply-To: <20260402002011.89926-1-rosenp@gmail.com>
Hi Rosen,
On Wed, Apr 01, 2026 at 05:20:11PM -0700, Rosen Penev wrote:
> Use a flexible array member to combine kzalloc and kcalloc in one
> allocation so they can be freed together.
>
> Add __counted_by for extra runtime analysis. Move counting variable
> assignment right after allocation as done by kzalloc_flex with GCC >=
> 15.
>
> Signed-off-by: Rosen Penev <rosenp@gmail.com>
> ---
> drivers/clk/mvebu/common.c | 19 ++++++++-----------
> 1 file changed, 8 insertions(+), 11 deletions(-)
>
> diff --git a/drivers/clk/mvebu/common.c b/drivers/clk/mvebu/common.c
> index 28f2e1b2a932..4129690fcae0 100644
> --- a/drivers/clk/mvebu/common.c
> +++ b/drivers/clk/mvebu/common.c
> @@ -189,10 +189,10 @@ DEFINE_SPINLOCK(ctrl_gating_lock);
>
> struct clk_gating_ctrl {
> spinlock_t *lock;
> - struct clk **gates;
> int num_gates;
> void __iomem *base;
> u32 saved_reg;
> + struct clk *gates[] __counted_by(num_gates);
> };
>
> static struct clk_gating_ctrl *ctrl;
> @@ -257,24 +257,21 @@ void __init mvebu_clk_gating_setup(struct device_node *np,
> clk_put(clk);
> }
>
> - ctrl = kzalloc_obj(*ctrl);
> + /* Count, allocate, and register clock gates */
> + for (n = 0; desc[n].name;)
> + n++;
> +
> + ctrl = kzalloc_flex(*ctrl, gates, n);
> if (WARN_ON(!ctrl))
> goto ctrl_out;
>
> + ctrl->num_gates = n;
> +
> /* lock must already be initialized */
> ctrl->lock = &ctrl_gating_lock;
>
> ctrl->base = base;
>
> - /* Count, allocate, and register clock gates */
> - for (n = 0; desc[n].name;)
> - n++;
> -
> - ctrl->num_gates = n;
> - ctrl->gates = kzalloc_objs(*ctrl->gates, ctrl->num_gates);
> - if (WARN_ON(!ctrl->gates))
> - goto gates_out;
The gates_out label and kfree() needs to be removed.
Brian
> -
> for (n = 0; n < ctrl->num_gates; n++) {
> const char *parent =
> (desc[n].parent) ? desc[n].parent : default_parent;
> --
> 2.53.0
>
prev parent reply other threads:[~2026-04-03 13:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-02 0:20 [PATCH] clk: mvebu: use kzalloc_flex Rosen Penev
2026-04-03 13:29 ` Brian Masney [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=ac_AtoG1j_I2m9Ja@redhat.com \
--to=bmasney@redhat.com \
--cc=andrew@lunn.ch \
--cc=gregory.clement@bootlin.com \
--cc=gustavoars@kernel.org \
--cc=kees@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=rosenp@gmail.com \
--cc=sboyd@kernel.org \
--cc=sebastian.hesselbarth@gmail.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