Depending of the memory size needed, we clear or not the allocated memory. This is not consistent. So remove the zeroing of the memory in the __vmalloc() case. Signed-off-by: Christophe JAILLET <christophe.jaillet@xxxxxxxxxx> --- This is just a guess. I don't know this code at all, but because of KVM, it is maybe safer to clear the memory in both cases? So, maybe it is better to use kzalloc() in the other path. --- arch/x86/kvm/svm/sev.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/x86/kvm/svm/sev.c b/arch/x86/kvm/svm/sev.c index 722186601c03..afd9485bef5a 100644 --- a/arch/x86/kvm/svm/sev.c +++ b/arch/x86/kvm/svm/sev.c @@ -434,7 +434,7 @@ static struct page **sev_pin_memory(struct kvm *kvm, unsigned long uaddr, /* Avoid using vmalloc for smaller buffers. */ size = npages * sizeof(struct page *); if (size > PAGE_SIZE) - pages = __vmalloc(size, GFP_KERNEL_ACCOUNT | __GFP_ZERO); + pages = __vmalloc(size, GFP_KERNEL_ACCOUNT); else pages = kmalloc(size, GFP_KERNEL_ACCOUNT); -- 2.44.0
