From: Paolo Bonzini <pbonzini@redhat.com>
To: "David Rientjes" <rientjes@google.com>,
"Radim Krčmář" <rkrcmar@redhat.com>,
"Joerg Roedel" <joro@8bytes.org>
Cc: Cfir Cohen <cfir@google.com>,
Brijesh Singh <brijesh.singh@amd.com>,
Tom Lendacky <thomas.lendacky@amd.com>,
x86@kernel.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [patch] kvm: svm: fix potential get_num_contig_pages overflow
Date: Fri, 5 Apr 2019 20:49:33 +0200 [thread overview]
Message-ID: <7a0590c0-330c-3144-94f2-3edcc7a92739@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1903191517380.256304@chino.kir.corp.google.com>
On 19/03/19 23:19, David Rientjes wrote:
> get_num_contig_pages() could potentially overflow int so make its type
> consistent with its usage.
>
> Reported-by: Cfir Cohen <cfir@google.com>
> Signed-off-by: David Rientjes <rientjes@google.com>
> ---
> arch/x86/kvm/svm.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/arch/x86/kvm/svm.c b/arch/x86/kvm/svm.c
> --- a/arch/x86/kvm/svm.c
> +++ b/arch/x86/kvm/svm.c
> @@ -6422,11 +6422,11 @@ static int sev_launch_start(struct kvm *kvm, struct kvm_sev_cmd *argp)
> return ret;
> }
>
> -static int get_num_contig_pages(int idx, struct page **inpages,
> - unsigned long npages)
> +static unsigned long get_num_contig_pages(unsigned long idx,
> + struct page **inpages, unsigned long npages)
> {
> unsigned long paddr, next_paddr;
> - int i = idx + 1, pages = 1;
> + unsigned long i = idx + 1, pages = 1;
>
> /* find the number of contiguous pages starting from idx */
> paddr = __sme_page_pa(inpages[idx]);
> @@ -6445,12 +6445,12 @@ static int get_num_contig_pages(int idx, struct page **inpages,
>
> static int sev_launch_update_data(struct kvm *kvm, struct kvm_sev_cmd *argp)
> {
> - unsigned long vaddr, vaddr_end, next_vaddr, npages, size;
> + unsigned long vaddr, vaddr_end, next_vaddr, npages, pages, size, i;
> struct kvm_sev_info *sev = &to_kvm_svm(kvm)->sev_info;
> struct kvm_sev_launch_update_data params;
> struct sev_data_launch_update_data *data;
> struct page **inpages;
> - int i, ret, pages;
> + int ret;
>
> if (!sev_guest(kvm))
> return -ENOTTY;
>
I had missed it, and now I've queued it.
Paolo
prev parent reply other threads:[~2019-04-05 18:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-19 22:19 David Rientjes
2019-03-20 14:07 ` Singh, Brijesh
2019-04-04 20:55 ` David Rientjes
2019-04-05 18:49 ` 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=7a0590c0-330c-3144-94f2-3edcc7a92739@redhat.com \
--to=pbonzini@redhat.com \
--cc=brijesh.singh@amd.com \
--cc=cfir@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rientjes@google.com \
--cc=rkrcmar@redhat.com \
--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®