stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Ovidiu Panait <ovidiu.panait@windriver.com>, stable@vger.kernel.org
Subject: Re: [PATCH v2 4.19 3/3] KVM: Use kvm_pfn_t for local PFN variable in hva_to_pfn_remapped()
Date: Tue, 27 Jul 2021 13:20:21 +0200	[thread overview]
Message-ID: <YP/r9VaOpLunpwCo@kroah.com> (raw)
In-Reply-To: <07f120ee-28fd-4521-495f-071a0d71a8cc@redhat.com>

On Tue, Jul 27, 2021 at 01:01:01PM +0200, Paolo Bonzini wrote:
> On 27/07/21 10:29, Ovidiu Panait wrote:
> > From: Sean Christopherson <seanjc@google.com>
> > 
> > commit a9545779ee9e9e103648f6f2552e73cfe808d0f4 upstream
> > 
> > Use kvm_pfn_t, a.k.a. u64, for the local 'pfn' variable when retrieving
> > a so called "remapped" hva/pfn pair.  In theory, the hva could resolve to
> > a pfn in high memory on a 32-bit kernel.
> > 
> > This bug was inadvertantly exposed by commit bd2fae8da794 ("KVM: do not
> > assume PTE is writable after follow_pfn"), which added an error PFN value
> > to the mix, causing gcc to comlain about overflowing the unsigned long.
> > 
> >    arch/x86/kvm/../../../virt/kvm/kvm_main.c: In function ‘hva_to_pfn_remapped’:
> >    include/linux/kvm_host.h:89:30: error: conversion from ‘long long unsigned int’
> >                                    to ‘long unsigned int’ changes value from
> >                                    ‘9218868437227405314’ to ‘2’ [-Werror=overflow]
> >     89 | #define KVM_PFN_ERR_RO_FAULT (KVM_PFN_ERR_MASK + 2)
> >        |                              ^
> > virt/kvm/kvm_main.c:1935:9: note: in expansion of macro ‘KVM_PFN_ERR_RO_FAULT’
> > 
> > Cc: stable@vger.kernel.org
> > Fixes: add6a0cd1c5b ("KVM: MMU: try to fix up page faults before giving up")
> > Signed-off-by: Sean Christopherson <seanjc@google.com>
> > Message-Id: <20210208201940.1258328-1-seanjc@google.com>
> > Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> > Signed-off-by: Ovidiu Panait <ovidiu.panait@windriver.com>
> > ---
> >   virt/kvm/kvm_main.c | 2 +-
> >   1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/virt/kvm/kvm_main.c b/virt/kvm/kvm_main.c
> > index 3559eba5f502..a3d82113ae1c 100644
> > --- a/virt/kvm/kvm_main.c
> > +++ b/virt/kvm/kvm_main.c
> > @@ -1501,7 +1501,7 @@ static int hva_to_pfn_remapped(struct vm_area_struct *vma,
> >   			       bool write_fault, bool *writable,
> >   			       kvm_pfn_t *p_pfn)
> >   {
> > -	unsigned long pfn;
> > +	kvm_pfn_t pfn;
> >   	pte_t *ptep;
> >   	spinlock_t *ptl;
> >   	int r;
> > 
> 
> Acked-by: Paolo Bonzini <pbonzini@redhat.com>
> 
> and the other two are the same as v1.

Thanks, now queued up.  I'll push out a new -rc with this added.

greg k-h

      reply	other threads:[~2021-07-27 11:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-27  8:29 [PATCH v2 4.19 1/3] KVM: do not assume PTE is writable after follow_pfn Ovidiu Panait
2021-07-27  8:29 ` [PATCH v2 4.19 2/3] KVM: do not allow mapping valid but non-reference-counted pages Ovidiu Panait
2021-07-27  8:29 ` [PATCH v2 4.19 3/3] KVM: Use kvm_pfn_t for local PFN variable in hva_to_pfn_remapped() Ovidiu Panait
2021-07-27 11:01   ` Paolo Bonzini
2021-07-27 11:20     ` Greg KH [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=YP/r9VaOpLunpwCo@kroah.com \
    --to=greg@kroah.com \
    --cc=ovidiu.panait@windriver.com \
    --cc=pbonzini@redhat.com \
    --cc=stable@vger.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;
as well as URLs for NNTP newsgroup(s).