[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220308105918.615575-1-pbonzini@redhat.com>
Date: Tue, 8 Mar 2022 05:59:15 -0500
From: Paolo Bonzini <pbonzini@...hat.com>
To: linux-kernel@...r.kernel.org, kvm@...r.kernel.org
Cc: Michael Ellerman <mpe@...erman.id.au>,
Andrew Morton <akpm@...ux-foundation.org>,
Dennis Zhou <dennis@...nel.org>, Tejun Heo <tj@...nel.org>,
Christoph Lameter <cl@...ux.com>,
Johannes Weiner <hannes@...xchg.org>,
Michal Hocko <mhocko@...nel.org>,
Vladimir Davydov <vdavydov.dev@...il.com>, linux-mm@...ck.org,
cgroups@...r.kernel.org
Subject: [PATCH 0/3] mm: vmalloc: introduce array allocation functions
The first patch in this series introduces four array allocation
functions to replace vmalloc(array_size()) and vzalloc(array_size()),
of which Linux has dozens of occurrences. The Functions take care of
the multiplication and overflow check, result in simpler code and make
it easier for developers to avoid overflow bugs.
The other two patches start to apply the functions in the mm/ and KVM
areas. In the case of KVM, it is also important to switch from kvcalloc
to __vcalloc; the allocation size is driven by userspace and can be larger
than 4GiB, which has been forbidden by the kv*alloc functions since 5.15.
Paolo
Paolo Bonzini (3):
mm: vmalloc: introduce array allocation functions
mm: use vmalloc_array and vcalloc for array allocations
KVM: use __vcalloc for very large allocations
arch/powerpc/kvm/book3s_hv_uvmem.c | 2 +-
arch/x86/kvm/mmu/page_track.c | 7 +++--
arch/x86/kvm/x86.c | 4 +--
include/linux/vmalloc.h | 5 +++
mm/percpu-stats.c | 2 +-
mm/swap_cgroup.c | 4 +--
mm/util.c | 50 ++++++++++++++++++++++++++++++
virt/kvm/kvm_main.c | 4 +--
9 files changed, 66 insertions(+), 12 deletions(-)
--
2.31.1
Powered by blists - more mailing lists