From: Lee Jones <lee@kernel.org>
To: Rosen Penev <rosenp@gmail.com>
Cc: linux-leds@vger.kernel.org, Pavel Machek <pavel@kernel.org>,
Kees Cook <kees@kernel.org>,
"Gustavo A. R. Silva" <gustavoars@kernel.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] leds: pca955x: kzalloc + kcalloc to single kzalloc
Date: Thu, 26 Mar 2026 11:33:36 +0000 [thread overview]
Message-ID: <20260326113336.GK1141718@google.com> (raw)
In-Reply-To: <20260320040821.46540-1-rosenp@gmail.com>
On Thu, 19 Mar 2026, Rosen Penev wrote:
> Two fewer allocations as a result.
>
> Required placing some structs before others as flexible array members
> require a complete definition. Declaration is not enough.
>
> Added __counted_by support for one of the structs for extra runtime
> analysis.
>
> Signed-off-by: Rosen Penev <rosenp@gmail.com>
> ---
> drivers/leds/leds-pca955x.c | 45 ++++++++++++++-----------------------
> 1 file changed, 17 insertions(+), 28 deletions(-)
>
> diff --git a/drivers/leds/leds-pca955x.c b/drivers/leds/leds-pca955x.c
> index 2007fe6217ec..ee5f02eaa3c9 100644
> --- a/drivers/leds/leds-pca955x.c
> +++ b/drivers/leds/leds-pca955x.c
> @@ -112,19 +112,6 @@ static const struct pca955x_chipdef pca955x_chipdefs[] = {
> },
> };
>
> -struct pca955x {
> - struct mutex lock;
> - struct pca955x_led *leds;
> - const struct pca955x_chipdef *chipdef;
> - struct i2c_client *client;
> - unsigned long active_blink;
> - unsigned long active_pins;
> - unsigned long blink_period;
> -#ifdef CONFIG_LEDS_PCA955X_GPIO
> - struct gpio_chip gpio;
> -#endif
> -};
> -
> struct pca955x_led {
> struct pca955x *pca955x;
> struct led_classdev led_cdev;
> @@ -137,8 +124,21 @@ struct pca955x_led {
> #define led_to_pca955x(l) container_of(l, struct pca955x_led, led_cdev)
>
> struct pca955x_platform_data {
> - struct pca955x_led *leds;
> int num_leds;
> + struct pca955x_led leds[] __counted_by(num_leds);
Where is the memory allocated to this now?
Why do we need this in both structs?
> +};
> +
> +struct pca955x {
> + struct mutex lock;
> + const struct pca955x_chipdef *chipdef;
> + struct i2c_client *client;
> + unsigned long active_blink;
> + unsigned long active_pins;
> + unsigned long blink_period;
> +#ifdef CONFIG_LEDS_PCA955X_GPIO
> + struct gpio_chip gpio;
> +#endif
> + struct pca955x_led leds[];
> };
>
> /* 8 bits per input register */
> @@ -542,15 +542,11 @@ pca955x_get_pdata(struct i2c_client *client, const struct pca955x_chipdef *chip)
> if (count > chip->bits)
> return ERR_PTR(-ENODEV);
>
> - pdata = devm_kzalloc(&client->dev, sizeof(*pdata), GFP_KERNEL);
> + pdata = devm_kzalloc(&client->dev, struct_size(pdata, leds, chip->bits), GFP_KERNEL);
> if (!pdata)
> return ERR_PTR(-ENOMEM);
>
> - pdata->leds = devm_kcalloc(&client->dev,
> - chip->bits, sizeof(struct pca955x_led),
> - GFP_KERNEL);
> - if (!pdata->leds)
> - return ERR_PTR(-ENOMEM);
> + pdata->num_leds = chip->bits;
>
> device_for_each_child_node(&client->dev, child) {
> u32 reg;
> @@ -568,8 +564,6 @@ pca955x_get_pdata(struct i2c_client *client, const struct pca955x_chipdef *chip)
> fwnode_property_read_u32(child, "type", &led->type);
> }
>
> - pdata->num_leds = chip->bits;
> -
> return pdata;
> }
>
> @@ -623,15 +617,10 @@ static int pca955x_probe(struct i2c_client *client)
> return -ENODEV;
> }
>
> - pca955x = devm_kzalloc(&client->dev, sizeof(*pca955x), GFP_KERNEL);
> + pca955x = devm_kzalloc(&client->dev, struct_size(pca955x, leds, chip->bits), GFP_KERNEL);
> if (!pca955x)
> return -ENOMEM;
>
> - pca955x->leds = devm_kcalloc(&client->dev, chip->bits,
> - sizeof(*pca955x_led), GFP_KERNEL);
> - if (!pca955x->leds)
> - return -ENOMEM;
> -
> i2c_set_clientdata(client, pca955x);
>
> mutex_init(&pca955x->lock);
> --
> 2.53.0
>
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2026-03-26 11:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-20 4:08 [PATCH] leds: pca955x: kzalloc + kcalloc to single kzalloc Rosen Penev
2026-03-26 11:33 ` Lee Jones [this message]
2026-03-26 19:04 ` Rosen Penev
2026-04-09 12:44 ` Lee Jones
2026-04-09 17:32 ` Rosen Penev
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=20260326113336.GK1141718@google.com \
--to=lee@kernel.org \
--cc=gustavoars@kernel.org \
--cc=kees@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@kernel.org \
--cc=rosenp@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