[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <e77238c5-94a6-0695-b49a-6ce6f4ccab70@redhat.com>
Date: Fri, 21 Feb 2020 17:58:05 +0100
From: Paolo Bonzini <pbonzini@...hat.com>
To: linmiaohe <linmiaohe@...wei.com>,
"Li,Rongqing" <lirongqing@...du.com>
Cc: Liran Alon <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>,
"vkuznets@...hat.com" <vkuznets@...hat.com>
Subject: Re: [PATCH][resend] KVM: fix error handling in svm_cpu_init
On 20/02/20 09:40, linmiaohe wrote:
> Li,Rongqing <lirongqing@...du.com> writes:
>>> Hi,
>>> Li RongQing <lirongqing@...du.com> writes:
>>>>
>>>> sd->save_area should be freed in error path
>>> Oh, it's strange. This is already fixed in my previous patch : [PATCH v2] KVM:
>>> SVM: Fix potential memory leak in svm_cpu_init().
>>> And Vitaly and Liran gave me Reviewed-by tags and Paolo queued it one
>>> month ago. But I can't found it in master or queue branch. There might
>>> be something wrong. :(
>>
>> In fact, I send this patch 2019/02/, and get Reviewed-by, but did not queue
>>
>> https://patchwork.kernel.org/patch/10853973/
>>
>> and resend it 2019/07
>>
>> https://patchwork.kernel.org/patch/11032081/
>>
>
> Oh, it's really a pit. And in this case, we can get rid of the var r as '-ENOMEM' is actually the only possible outcome here, as
> suggested by Vitaly, which looks like this: https://lkml.org/lkml/2020/1/15/933
I queued your patch again, sorry to both of you.
Paolo
Powered by blists - more mailing lists