[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <b7a41c2ec0e644119180ba61d10ab4b9@huawei.com>
Date: Thu, 20 Feb 2020 08:40:36 +0000
From: linmiaohe <linmiaohe@...wei.com>
To: "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>,
"pbonzini@...hat.com" <pbonzini@...hat.com>,
"vkuznets@...hat.com" <vkuznets@...hat.com>
Subject: Re: [PATCH][resend] KVM: fix error handling in svm_cpu_init
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
Thanks. :)
Powered by blists - more mailing lists