* Re: [PATCH] KVM: X86: fix a bad_page bug_on path
2017-10-13 21:48 [PATCH] KVM: X86: fix a bad_page bug_on path Peng Hao
@ 2017-10-13 15:04 ` Paolo Bonzini
0 siblings, 0 replies; 2+ messages in thread
From: Paolo Bonzini @ 2017-10-13 15:04 UTC (permalink / raw)
To: Peng Hao, rkrcmar; +Cc: x86, kvm, linux-kernel, Junaid Shahid, Xiao Guangrong
On 13/10/2017 23:48, Peng Hao wrote:
> When poweroff L1 Guest with L2 guset on L1, it exists a path to
> trigger a bad_page bug_on.
How easy it is to reproduce? CCing Junaid and Guangrong too.
> !page_count(pfn_to_page(pfn)) Warning in mmu_spte_clear_track_bits will
> appear before,then it may set A/D bit for the freed page and trigger a
> bad_page bug_on.
>
> Signed-off-by: Peng Hao <peng.hao2@zte.com.cn>
> ---
> arch/x86/kvm/mmu.c | 8 ++------
> 1 file changed, 2 insertions(+), 6 deletions(-)
>
> diff --git a/arch/x86/kvm/mmu.c b/arch/x86/kvm/mmu.c
> index eca30c1..398de96 100644
> --- a/arch/x86/kvm/mmu.c
> +++ b/arch/x86/kvm/mmu.c
> @@ -711,12 +711,8 @@ static int mmu_spte_clear_track_bits(u64 *sptep)
>
> pfn = spte_to_pfn(old_spte);
>
> - /*
> - * KVM does not hold the refcount of the page used by
> - * kvm mmu, before reclaiming the page, we should
> - * unmap it from mmu first.
> - */
> - WARN_ON(!kvm_is_reserved_pfn(pfn) && !page_count(pfn_to_page(pfn)));
> + if (!page_count(pfn_to_page(pfn)))
> + return 1;
If the page count is zero, KVM should not have accessed this page at
all. The bug is elsewhere. :(
Paolo
> if (is_accessed_spte(old_spte))
> kvm_set_pfn_accessed(pfn);
>
^ permalink raw reply [flat|nested] 2+ messages in thread
* [PATCH] KVM: X86: fix a bad_page bug_on path
@ 2017-10-13 21:48 Peng Hao
2017-10-13 15:04 ` Paolo Bonzini
0 siblings, 1 reply; 2+ messages in thread
From: Peng Hao @ 2017-10-13 21:48 UTC (permalink / raw)
To: pbonzini, rkrcmar; +Cc: x86, kvm, linux-kernel, Peng Hao
When poweroff L1 Guest with L2 guset on L1, it exists a path to
trigger a bad_page bug_on.
!page_count(pfn_to_page(pfn)) Warning in mmu_spte_clear_track_bits will
appear before,then it may set A/D bit for the freed page and trigger a
bad_page bug_on.
Signed-off-by: Peng Hao <peng.hao2@zte.com.cn>
---
arch/x86/kvm/mmu.c | 8 ++------
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/arch/x86/kvm/mmu.c b/arch/x86/kvm/mmu.c
index eca30c1..398de96 100644
--- a/arch/x86/kvm/mmu.c
+++ b/arch/x86/kvm/mmu.c
@@ -711,12 +711,8 @@ static int mmu_spte_clear_track_bits(u64 *sptep)
pfn = spte_to_pfn(old_spte);
- /*
- * KVM does not hold the refcount of the page used by
- * kvm mmu, before reclaiming the page, we should
- * unmap it from mmu first.
- */
- WARN_ON(!kvm_is_reserved_pfn(pfn) && !page_count(pfn_to_page(pfn)));
+ if (!page_count(pfn_to_page(pfn)))
+ return 1;
if (is_accessed_spte(old_spte))
kvm_set_pfn_accessed(pfn);
--
1.8.3.1
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2017-10-13 15:04 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-10-13 21:48 [PATCH] KVM: X86: fix a bad_page bug_on path Peng Hao
2017-10-13 15:04 ` Paolo Bonzini
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®