[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aPYHPmebIcGxeywe@milan>
Date: Mon, 20 Oct 2025 11:56:14 +0200
From: Uladzislau Rezki <urezki@...il.com>
To: Mehdi Ben Hadj Khelifa <mehdi.benhadjkhelifa@...il.com>
Cc: akpm@...ux-foundation.org, urezki@...il.com, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, skhan@...uxfoundation.org,
david.hunter.linux@...il.com,
linux-kernel-mentees@...ts.linuxfoundation.org, khalid@...nel.org
Subject: Re: [PATCH] mm/vmalloc: Use kmalloc_array() instead of kmalloc()
On Sat, Oct 18, 2025 at 09:11:48PM +0100, Mehdi Ben Hadj Khelifa wrote:
> The number of NUMA nodes (nr_node_ids) is bounded, so overflow is not a
> practical concern here. However, using kmalloc_array() better reflects the
> intent to allocate an array of unsigned ints, and improves consistency with
> other NUMA-related allocations.
>
> No functional change intended.
>
> Signed-off-by: Mehdi Ben Hadj Khelifa <mehdi.benhadjkhelifa@...il.com>
> ---
> mm/vmalloc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/mm/vmalloc.c b/mm/vmalloc.c
> index 798b2ed21e46..697bc171b013 100644
> --- a/mm/vmalloc.c
> +++ b/mm/vmalloc.c
> @@ -5055,7 +5055,7 @@ static int vmalloc_info_show(struct seq_file *m, void *p)
> unsigned int *counters;
>
> if (IS_ENABLED(CONFIG_NUMA))
> - counters = kmalloc(nr_node_ids * sizeof(unsigned int), GFP_KERNEL);
> + counters = kmalloc_array(nr_node_ids, sizeof(unsigned int), GFP_KERNEL);
>
> for_each_vmap_node(vn) {
> spin_lock(&vn->busy.lock);
> --
> 2.51.1.dirty
>
Reviewed-by: Uladzislau Rezki (Sony) <urezki@...il.com>
Thank you!
--
Uladzislau Rezki
Powered by blists - more mailing lists