On Tue, 8 Mar 2022 05:59:18 -0500 Paolo Bonzini <pbonzini@xxxxxxxxxx> wrote: > Allocations whose size is related to the memslot size can be arbitrarily > large. Do not use kvzalloc/kvcalloc, as those are limited to "not crazy" > sizes that fit in 32 bits. Now that it is available, they can use either > vcalloc or __vcalloc, the latter if accounting is required. > > Cc: stable@xxxxxxxxxxxxxxx Please fully describe the end user visible runtime effects when proposing a -stable backport. And when not proposing a -stable backport, come to that...
