[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <7743ff8a-1492-4191-95ec-abcb53001b83@paulmck-laptop>
Date: Mon, 21 Apr 2025 06:49:54 -0700
From: "Paul E. McKenney" <paulmck@...nel.org>
To: Su Hui <suhui@...china.com>
Cc: dave@...olabs.net, josh@...htriplett.org, frederic@...nel.org,
neeraj.upadhyay@...nel.org, joel@...lfernandes.org,
boqun.feng@...il.com, urezki@...il.com, rostedt@...dmis.org,
mathieu.desnoyers@...icios.com, jiangshanlai@...il.com,
qiang.zhang1211@...il.com, linux-kernel@...r.kernel.org,
rcu@...r.kernel.org, kernel-janitors@...r.kernel.org,
linux-hardening@...r.kernel.org
Subject: Re: [PATCH] rcuscale: using kmalloc_array() to relpace kmalloc()
On Mon, Apr 21, 2025 at 02:15:09PM +0800, Su Hui wrote:
> It's safer to using kmalloc_array() because it can prevent overflow
> problem.
>
> Signed-off-by: Su Hui <suhui@...china.com>
Thank you!
But isn't kcalloc just a wrapper around kmalloc_array() anyway?
Thanx, Paul
> ---
> kernel/rcu/rcuscale.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/rcu/rcuscale.c b/kernel/rcu/rcuscale.c
> index 0f3059b1b80d..cbe2195f08d6 100644
> --- a/kernel/rcu/rcuscale.c
> +++ b/kernel/rcu/rcuscale.c
> @@ -762,7 +762,7 @@ kfree_scale_thread(void *arg)
> }
>
> for (i = 0; i < kfree_alloc_num; i++) {
> - alloc_ptr = kmalloc(kfree_mult * sizeof(struct kfree_obj), GFP_KERNEL);
> + alloc_ptr = kmalloc_array(kfree_mult, sizeof(struct kfree_obj), GFP_KERNEL);
> if (!alloc_ptr)
> return -ENOMEM;
>
> --
> 2.30.2
>
>
Powered by blists - more mailing lists