From: Paolo Bonzini <pbonzini@redhat.com>
To: Ashish Kalra <Ashish.Kalra@amd.com>
Cc: tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
joro@8bytes.org, bp@suse.de, thomas.lendacky@amd.com,
Brijesh.Singh@amd.com, x86@kernel.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, ssg.sos.patches@amd.com
Subject: Re: [PATCH] KVM: SVM: Fix offset computation bug in __sev_dbg_decrypt().
Date: Mon, 16 Nov 2020 19:59:05 +0100 [thread overview]
Message-ID: <d9f6ac9b-0655-6403-aa4e-4dc70f519b28@redhat.com> (raw)
In-Reply-To: <20201110224205.29444-1-Ashish.Kalra@amd.com>
On 10/11/20 23:42, Ashish Kalra wrote:
> From: Ashish Kalra <ashish.kalra@amd.com>
>
> Fix offset computation in __sev_dbg_decrypt() to include the
> source paddr before it is rounded down to be aligned to 16 bytes
> as required by SEV API. This fixes incorrect guest memory dumps
> observed when using qemu monitor.
>
> Signed-off-by: Ashish Kalra <ashish.kalra@amd.com>
> ---
> 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 c0b14106258a..566f4d18185b 100644
> --- a/arch/x86/kvm/svm/sev.c
> +++ b/arch/x86/kvm/svm/sev.c
> @@ -642,8 +642,8 @@ static int __sev_dbg_decrypt(struct kvm *kvm, unsigned long src_paddr,
> * Its safe to read more than we are asked, caller should ensure that
> * destination has enough space.
> */
> - src_paddr = round_down(src_paddr, 16);
> offset = src_paddr & 15;
> + src_paddr = round_down(src_paddr, 16);
> sz = round_up(sz + offset, 16);
>
> return __sev_issue_dbg_cmd(kvm, src_paddr, dst_paddr, sz, err, false);
>
I just missed it. Queued now, thanks.
Paolo
prev parent reply other threads:[~2020-11-16 18:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-10 22:42 Ashish Kalra
2020-11-16 18:59 ` Paolo Bonzini [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=d9f6ac9b-0655-6403-aa4e-4dc70f519b28@redhat.com \
--to=pbonzini@redhat.com \
--cc=Ashish.Kalra@amd.com \
--cc=Brijesh.Singh@amd.com \
--cc=bp@suse.de \
--cc=hpa@zytor.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=ssg.sos.patches@amd.com \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.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
all inboxes | Powered by JetHome®