From: Michal Hocko <mhocko@suse.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
Michael Ellerman <mpe@ellerman.id.au>,
Andrew Morton <akpm@linux-foundation.org>,
Dennis Zhou <dennis@kernel.org>, Tejun Heo <tj@kernel.org>,
Christoph Lameter <cl@linux.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Vladimir Davydov <vdavydov.dev@gmail.com>,
linux-mm@kvack.org, cgroups@vger.kernel.org
Subject: Re: [PATCH 2/3] mm: use vmalloc_array and vcalloc for array allocations
Date: Tue, 8 Mar 2022 14:49:01 +0100 [thread overview]
Message-ID: <YidezSPVZBCQcGJ4@dhcp22.suse.cz> (raw)
In-Reply-To: <20220308105918.615575-3-pbonzini@redhat.com>
On Tue 08-03-22 05:59:17, Paolo Bonzini wrote:
> Instead of using array_size or just a multiply, use a function that
> takes care of both the multiplication and the overflow checks.
>
> Cc: linux-mm@kvack.org
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Acked-by: Michal Hocko <mhocko@suse.com>
The resulting code is easier to read indeed.
> ---
> mm/percpu-stats.c | 2 +-
> mm/swap_cgroup.c | 4 +---
> 2 files changed, 2 insertions(+), 4 deletions(-)
>
> diff --git a/mm/percpu-stats.c b/mm/percpu-stats.c
> index c6bd092ff7a3..e71651cda2de 100644
> --- a/mm/percpu-stats.c
> +++ b/mm/percpu-stats.c
> @@ -144,7 +144,7 @@ static int percpu_stats_show(struct seq_file *m, void *v)
> spin_unlock_irq(&pcpu_lock);
>
> /* there can be at most this many free and allocated fragments */
> - buffer = vmalloc(array_size(sizeof(int), (2 * max_nr_alloc + 1)));
> + buffer = vmalloc_array(2 * max_nr_alloc + 1, sizeof(int));
> if (!buffer)
> return -ENOMEM;
>
> diff --git a/mm/swap_cgroup.c b/mm/swap_cgroup.c
> index 7f34343c075a..5a9442979a18 100644
> --- a/mm/swap_cgroup.c
> +++ b/mm/swap_cgroup.c
> @@ -167,14 +167,12 @@ unsigned short lookup_swap_cgroup_id(swp_entry_t ent)
> int swap_cgroup_swapon(int type, unsigned long max_pages)
> {
> void *array;
> - unsigned long array_size;
> unsigned long length;
> struct swap_cgroup_ctrl *ctrl;
>
> length = DIV_ROUND_UP(max_pages, SC_PER_PAGE);
> - array_size = length * sizeof(void *);
>
> - array = vzalloc(array_size);
> + array = vcalloc(length, sizeof(void *));
> if (!array)
> goto nomem;
>
> --
> 2.31.1
>
>
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2022-03-08 13:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 10:59 [PATCH 0/3] mm: vmalloc: introduce array allocation functions Paolo Bonzini
2022-03-08 10:59 ` [PATCH 1/3] " Paolo Bonzini
2022-03-08 13:47 ` Michal Hocko
2022-03-08 13:55 ` Paolo Bonzini
2022-03-08 15:26 ` Michal Hocko
2022-03-08 14:26 ` David Hildenbrand
2022-03-08 10:59 ` [PATCH 2/3] mm: use vmalloc_array and vcalloc for array allocations Paolo Bonzini
2022-03-08 13:49 ` Michal Hocko [this message]
2022-03-08 14:27 ` David Hildenbrand
2022-03-08 16:13 ` Dennis Zhou
2022-03-08 10:59 ` [PATCH 3/3] KVM: use vcalloc/__vcalloc for very large allocations Paolo Bonzini
2022-03-08 14:25 ` David Hildenbrand
2022-03-10 4:18 ` Andrew Morton
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=YidezSPVZBCQcGJ4@dhcp22.suse.cz \
--to=mhocko@suse.com \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=cl@linux.com \
--cc=dennis@kernel.org \
--cc=hannes@cmpxchg.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mpe@ellerman.id.au \
--cc=pbonzini@redhat.com \
--cc=tj@kernel.org \
--cc=vdavydov.dev@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