[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <77a34051-2672-88cf-99dd-60f5acfb905e@redhat.com>
Date: Tue, 8 Mar 2022 14:55:39 +0100
From: Paolo Bonzini <pbonzini@...hat.com>
To: Michal Hocko <mhocko@...e.com>
Cc: linux-kernel@...r.kernel.org, kvm@...r.kernel.org,
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>,
Vladimir Davydov <vdavydov.dev@...il.com>, linux-mm@...ck.org,
cgroups@...r.kernel.org, stable@...r.kernel.org
Subject: Re: [PATCH 1/3] mm: vmalloc: introduce array allocation functions
On 3/8/22 14:47, Michal Hocko wrote:
> Seems useful
> Acked-by: Michal Hocko<mhocko@...e.com>
>
> Is there any reason you haven't used __alloc_size(1, 2) annotation?
It's enough to have them in the header:
>> +extern void *__vmalloc_array(size_t n, size_t size, gfp_t flags) __alloc_size(1, 2);
>> +extern void *vmalloc_array(size_t n, size_t size) __alloc_size(1, 2);
>> +extern void *__vcalloc(size_t n, size_t size, gfp_t flags) __alloc_size(1, 2);
>> +extern void *vcalloc(size_t n, size_t size) __alloc_size(1, 2);
Thanks for the quick review!
Paolo
Powered by blists - more mailing lists