From: "Li,Rongqing" <lirongqing@baidu.com>
To: linmiaohe <linmiaohe@huawei.com>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"vkuznets@redhat.com" <vkuznets@redhat.com>
Cc: Liran Alon <liran.alon@oracle.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>
Subject: 答复: [PATCH][resend] KVM: fix error handling in svm_cpu_init
Date: Thu, 20 Feb 2020 08:31:32 +0000 [thread overview]
Message-ID: <4d0b722be5cc4343a9fc9557dfbd00a1@baidu.com> (raw)
In-Reply-To: <4cf5d767b570430a9e0b515a9d6d8fbd@huawei.com>
> -----邮件原件-----
> 发件人: linmiaohe [mailto:linmiaohe@huawei.com]
> 发送时间: 2020年2月20日 16:18
> 收件人: Li,Rongqing <lirongqing@baidu.com>; pbonzini@redhat.com;
> vkuznets@redhat.com
> 抄送: Liran Alon <liran.alon@oracle.com>; kvm@vger.kernel.org;
> linux-kernel@vger.kernel.org; x86@kernel.org
> 主题: Re: [PATCH][resend] KVM: fix error handling in svm_cpu_init
>
> Hi,
> Li RongQing <lirongqing@baidu.com> writes:
> >
> >sd->save_area should be freed in error path
> >
> >Fixes: 70cd94e60c733 ("KVM: SVM: VMRUN should use associated ASID when
> >SEV is enabled")
> >Signed-off-by: Li RongQing <lirongqing@baidu.com>
> >Reviewed-by: Brijesh Singh <brijesh.singh@amd.com>
> >Reviewed-by: Vitaly Kuznetsov <vkuznets@redhat.com>
> >---
> > arch/x86/kvm/svm.c | 8 +++++---
> > 1 file changed, 5 insertions(+), 3 deletions(-)
>
> 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/
-Li
prev parent reply other threads:[~2020-02-20 9:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-20 8:18 linmiaohe
2020-02-20 8:31 ` Li,Rongqing [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4d0b722be5cc4343a9fc9557dfbd00a1@baidu.com \
--to=lirongqing@baidu.com \
--cc=kvm@vger.kernel.org \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liran.alon@oracle.com \
--cc=pbonzini@redhat.com \
--cc=vkuznets@redhat.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome