From: Xiao Guangrong <guangrong.xiao@linux.intel.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: gleb@kernel.org, mtosatti@redhat.com, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] KVM: MMU: fix smap permission check
Date: Thu, 07 May 2015 17:50:40 +0800 [thread overview]
Message-ID: <554B3570.10804@linux.intel.com> (raw)
In-Reply-To: <554B311D.2010701@redhat.com>
On 05/07/2015 05:32 PM, Paolo Bonzini wrote:
>
>
> On 07/05/2015 10:20, Xiao Guangrong wrote:
>> Current permission check assumes that RSVD bit in PFEC is always zero,
>> however, it is not true since MMIO #PF will use it to quickly identify
>> MMIO access
>>
>> Fix it by clearing the bit if walking guest page table is needed
>>
>> Signed-off-by: Xiao Guangrong <guangrong.xiao@linux.intel.com>
>> ---
>> arch/x86/kvm/mmu.h | 2 ++
>> arch/x86/kvm/paging_tmpl.h | 7 +++++++
>> 2 files changed, 9 insertions(+)
>>
>> diff --git a/arch/x86/kvm/mmu.h b/arch/x86/kvm/mmu.h
>> index c7d6563..06eb2fc 100644
>> --- a/arch/x86/kvm/mmu.h
>> +++ b/arch/x86/kvm/mmu.h
>> @@ -166,6 +166,8 @@ static inline bool permission_fault(struct kvm_vcpu *vcpu, struct kvm_mmu *mmu,
>> int index = (pfec >> 1) +
>> (smap >> (X86_EFLAGS_AC_BIT - PFERR_RSVD_BIT + 1));
>>
>> + WARN_ON(pfec & PFERR_RSVD_MASK);
>> +
>> return (mmu->permissions[index] >> pte_access) & 1;
>> }
>>
>> diff --git a/arch/x86/kvm/paging_tmpl.h b/arch/x86/kvm/paging_tmpl.h
>> index fd49c86..6e6d115 100644
>> --- a/arch/x86/kvm/paging_tmpl.h
>> +++ b/arch/x86/kvm/paging_tmpl.h
>> @@ -718,6 +718,13 @@ static int FNAME(page_fault)(struct kvm_vcpu *vcpu, gva_t addr, u32 error_code,
>> mmu_is_nested(vcpu));
>> if (likely(r != RET_MMIO_PF_INVALID))
>> return r;
>> +
>> + /*
>> + * page fault with PFEC.RSVD = 1 is caused by shadow
>> + * page fault, should not be used to walk guest page
>> + * table.
>> + */
>> + error_code &= ~PFERR_RSVD_MASK;
>> };
>>
>> r = mmu_topup_memory_caches(vcpu);
>>
>
> Applied.
>
> For the other patches I'm waiting for an answer re. kvm_mmu_pte_write.
Sure. Actually, i noticed these bugs when i was reviewing your patches,
will continue to review soon. :)
next prev parent reply other threads:[~2015-05-07 9:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-07 8:20 [PATCH 0/3] KVM: MMU: fix SMAP virtualization Xiao Guangrong
2015-05-07 8:20 ` [PATCH 1/3] KVM: MMU: fix smap permission check Xiao Guangrong
2015-05-07 9:32 ` Paolo Bonzini
2015-05-07 9:50 ` Xiao Guangrong [this message]
2015-05-07 8:20 ` [PATCH 2/3] KVM: MMU: fix SMAP virtualization Xiao Guangrong
2015-05-11 13:17 ` [PATCH v2 " Xiao Guangrong
2015-05-11 13:41 ` Paolo Bonzini
2015-05-07 8:20 ` [PATCH 3/3] KVM: MMU: document smap_andnot_wp Xiao Guangrong
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=554B3570.10804@linux.intel.com \
--to=guangrong.xiao@linux.intel.com \
--cc=gleb@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
/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