[<prev] [next>] [day] [month] [year] [list]
Message-ID: <9083833afd7c465a9222e6801cb66499@huawei.com>
Date: Fri, 3 Jan 2020 02:19:33 +0000
From: linmiaohe <linmiaohe@...wei.com>
To: Vitaly Kuznetsov <vkuznets@...hat.com>
CC: "liran.alon@...cle.com" <liran.alon@...cle.com>,
"kvm@...r.kernel.org" <kvm@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"x86@...nel.org" <x86@...nel.org>,
"pbonzini@...hat.com" <pbonzini@...hat.com>,
"rkrcmar@...hat.com" <rkrcmar@...hat.com>,
"sean.j.christopherson@...el.com" <sean.j.christopherson@...el.com>,
"wanpengli@...cent.com" <wanpengli@...cent.com>,
"jmattson@...gle.com" <jmattson@...gle.com>,
"joro@...tes.org" <joro@...tes.org>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"mingo@...hat.com" <mingo@...hat.com>,
"bp@...en8.de" <bp@...en8.de>, "hpa@...or.com" <hpa@...or.com>
Subject: Re: [PATCH] KVM: SVM: Fix potential memory leak in svm_cpu_init()
Vitaly writes:
>> From: Miaohe Lin <linmiaohe@...wei.com>
>> if (svm_sev_enabled()) {
>> r = -ENOMEM;
>
>Not your fault but this assignment to 'r' seem to be redundant: it is already set to '-ENOMEM' above, but this is also not perfect as ...
>
>> @@ -1020,14 +1020,16 @@ static int svm_cpu_init(int cpu)
>> sizeof(void *),
>> return r;
>
>... '-ENOMEM' is actually the only possible outcome here. In case you'll be re-submitting, I'd suggest we drop 'r' entirely and just reture -ENOMEM here.
The var r is really unnecessary and we should clean it up. Thanks for your good suggest. I would send a patch v2 soon.
>
>Anyways, your patch seems to be correct, so:
>
>Reviewed-by: Vitaly Kuznetsov <vkuznets@...hat.com>
Thanks for your review.
Powered by blists - more mailing lists