The Linux Kernel Mailing List
 help / color / mirror / Atom feed
* Re: [PATCHv3] ARM: omap2: simplify allocation for omap_device
       [not found] <20260330213528.18187-1-rosenp@gmail.com>
@ 2026-05-08 19:12 ` Kevin Hilman
  2026-05-11 16:51 ` Kevin Hilman
  1 sibling, 0 replies; 2+ messages in thread
From: Kevin Hilman @ 2026-05-08 19:12 UTC (permalink / raw)
  To: Rosen Penev, linux-omap
  Cc: Aaro Koskinen, Andreas Kemnade, Roger Quadros, Tony Lindgren,
	Russell King, Kees Cook, Gustavo A. R. Silva,
	moderated list:ARM SUB-ARCHITECTURES, open list,
	open list:KERNEL HARDENING (not covered by other areas):Keyword:b__counted_by(_le|_be)?b

Rosen Penev <rosenp@gmail.com> writes:

> Use a flexible array member (FAM) to combine hwmods array allocation
> with the omap_device structure. This reduces the number of allocations
> from two separate calls (one for the device, one for the array) to a
> single allocation, improving efficiency and reducing memory fragmentation.
>
> The FAM approach also enables bounds checking through __counted_by(),
> which provides runtime verification that array accesses stay within
> the allocated size. This improves security and helps catch bugs during
> development.
>
> Simplify error handling by removing the unnecessary multi-label goto
> pattern. The new code is more straightforward: allocate, verify, copy
> data, and either return success or error immediately.
>
> Also removes the now-redundant kfree(od->hwmods) in omap_device_delete()
> since the hwmods array is now embedded in the structure rather than
> separately allocated.
>
> Signed-off-by: Rosen Penev <rosenp@gmail.com>

Thanks for this cleanup.

> ---
>  v3: add a verbose description explaining why. Powered by Claude Sonnet
>  4.5.
>  v2: remove kfree and fix compilation.
>  arch/arm/mach-omap2/omap_device.c | 29 ++++++++++-------------------
>  arch/arm/mach-omap2/omap_device.h |  4 ++--
>  2 files changed, 12 insertions(+), 21 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/omap_device.c b/arch/arm/mach-omap2/omap_device.c
> index 79db4c49ffc9..77a75b0b9ae6 100644
> --- a/arch/arm/mach-omap2/omap_device.c
> +++ b/arch/arm/mach-omap2/omap_device.c
> @@ -307,35 +307,27 @@ static struct omap_device *omap_device_alloc(struct platform_device *pdev,
>  	int ret = -ENOMEM;
>  	struct omap_device *od;
>  	int i;
> -	struct omap_hwmod **hwmods;
> +	struct omap_hwmod *hwmod;
>
> -	od = kzalloc_obj(struct omap_device);
> -	if (!od)
> -		goto oda_exit1;
> +	od = kzalloc_flex(*od, hwmods, oh_cnt);
> +	if (!od) {
> +		dev_err(&pdev->dev, "omap_device: build failed (%d)\n", ret);
> +		return ERR_PTR(ret);
> +	}
>
>  	od->hwmods_cnt = oh_cnt;

minor nit: isn't this assignment redundant now, as kalloc_flex() should
assign the count?

> +	memcpy(od->hwmods, ohs, oh_cnt * sizeof(*od->hwmods));
>

> -	hwmods = kmemdup_array(ohs, oh_cnt, sizeof(*hwmods), GFP_KERNEL);
> -	if (!hwmods)
> -		goto oda_exit2;
> -
> -	od->hwmods = hwmods;
>  	od->pdev = pdev;
>  	pdev->archdata.od = od;
>
>  	for (i = 0; i < oh_cnt; i++) {
> -		hwmods[i]->od = od;
> -		_add_hwmod_clocks_clkdev(od, hwmods[i]);
> +		hwmod = od->hwmods[i];
> +		hwmod->od = od;
> +		_add_hwmod_clocks_clkdev(od, hwmod);
>  	}
>
>  	return od;
> -
> -oda_exit2:
> -	kfree(od);
> -oda_exit1:
> -	dev_err(&pdev->dev, "omap_device: build failed (%d)\n", ret);
> -
> -	return ERR_PTR(ret);
>  }

Kevin

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [PATCHv3] ARM: omap2: simplify allocation for omap_device
       [not found] <20260330213528.18187-1-rosenp@gmail.com>
  2026-05-08 19:12 ` [PATCHv3] ARM: omap2: simplify allocation for omap_device Kevin Hilman
@ 2026-05-11 16:51 ` Kevin Hilman
  1 sibling, 0 replies; 2+ messages in thread
From: Kevin Hilman @ 2026-05-11 16:51 UTC (permalink / raw)
  To: linux-omap, Rosen Penev
  Cc: Aaro Koskinen, Andreas Kemnade, Roger Quadros, Tony Lindgren,
	Russell King, Kees Cook, Gustavo A. R. Silva, linux-arm-kernel,
	linux-kernel, linux-hardening


On Mon, 30 Mar 2026 14:35:28 -0700, Rosen Penev wrote:
> Use a flexible array member (FAM) to combine hwmods array allocation
> with the omap_device structure. This reduces the number of allocations
> from two separate calls (one for the device, one for the array) to a
> single allocation, improving efficiency and reducing memory fragmentation.
> 
> The FAM approach also enables bounds checking through __counted_by(),
> which provides runtime verification that array accesses stay within
> the allocated size. This improves security and helps catch bugs during
> development.
> 
> [...]

Applied, thanks!

[1/1] ARM: omap2: simplify allocation for omap_device
      commit: 2a7a9e20b9e8b5dc4fdef777e67d390dcb3a8ea4

Best regards,
-- 
Kevin Hilman (TI) <khilman@baylibre.com>


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2026-05-11 16:51 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <20260330213528.18187-1-rosenp@gmail.com>
2026-05-08 19:12 ` [PATCHv3] ARM: omap2: simplify allocation for omap_device Kevin Hilman
2026-05-11 16:51 ` Kevin Hilman

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox