From: Paolo Bonzini <pbonzini@redhat.com>
To: Liang Zhang <zhangliang5@huawei.com>,
tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
dave.hansen@linux.intel.com, x86@kernel.org
Cc: seanjc@google.com, vkuznets@redhat.com, wanpengli@tencent.com,
jmattson@google.com, joro@8bytes.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, wangzhigang17@huawei.com
Subject: Re: [RESEND PATCH] KVM: x86/mmu: make apf token non-zero to fix bug
Date: Tue, 22 Feb 2022 09:38:38 +0100 [thread overview]
Message-ID: <6b5b8f01-6676-e7e4-d6d6-55c69f99a86d@redhat.com> (raw)
In-Reply-To: <20220222031239.1076682-1-zhangliang5@huawei.com>
On 2/22/22 04:12, Liang Zhang wrote:
> In current async pagefault logic, when a page is ready, KVM relies on
> kvm_arch_can_dequeue_async_page_present() to determine whether to deliver
> a READY event to the Guest. This function test token value of struct
> kvm_vcpu_pv_apf_data, which must be reset to zero by Guest kernel when a
> READY event is finished by Guest. If value is zero meaning that a READY
> event is done, so the KVM can deliver another.
> But the kvm_arch_setup_async_pf() may produce a valid token with zero
> value, which is confused with previous mention and may lead the loss of
> this READY event.
>
> This bug may cause task blocked forever in Guest:
> INFO: task stress:7532 blocked for more than 1254 seconds.
> Not tainted 5.10.0 #16
> "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> task:stress state:D stack: 0 pid: 7532 ppid: 1409
> flags:0x00000080
> Call Trace:
> __schedule+0x1e7/0x650
> schedule+0x46/0xb0
> kvm_async_pf_task_wait_schedule+0xad/0xe0
> ? exit_to_user_mode_prepare+0x60/0x70
> __kvm_handle_async_pf+0x4f/0xb0
> ? asm_exc_page_fault+0x8/0x30
> exc_page_fault+0x6f/0x110
> ? asm_exc_page_fault+0x8/0x30
> asm_exc_page_fault+0x1e/0x30
> RIP: 0033:0x402d00
> RSP: 002b:00007ffd31912500 EFLAGS: 00010206
> RAX: 0000000000071000 RBX: ffffffffffffffff RCX: 00000000021a32b0
> RDX: 000000000007d011 RSI: 000000000007d000 RDI: 00000000021262b0
> RBP: 00000000021262b0 R08: 0000000000000003 R09: 0000000000000086
> R10: 00000000000000eb R11: 00007fefbdf2baa0 R12: 0000000000000000
> R13: 0000000000000002 R14: 000000000007d000 R15: 0000000000001000
>
> Signed-off-by: Liang Zhang <zhangliang5@huawei.com>
> ---
> arch/x86/kvm/mmu/mmu.c | 13 ++++++++++++-
> 1 file changed, 12 insertions(+), 1 deletion(-)
>
> diff --git a/arch/x86/kvm/mmu/mmu.c b/arch/x86/kvm/mmu/mmu.c
> index 593093b52395..8e24f73bf60b 100644
> --- a/arch/x86/kvm/mmu/mmu.c
> +++ b/arch/x86/kvm/mmu/mmu.c
> @@ -3889,12 +3889,23 @@ static void shadow_page_table_clear_flood(struct kvm_vcpu *vcpu, gva_t addr)
> walk_shadow_page_lockless_end(vcpu);
> }
>
> +static u32 alloc_apf_token(struct kvm_vcpu *vcpu)
> +{
> + /* make sure the token value is not 0 */
> + u32 id = vcpu->arch.apf.id;
> +
> + if (id << 12 == 0)
> + vcpu->arch.apf.id = 1;
> +
> + return (vcpu->arch.apf.id++ << 12) | vcpu->vcpu_id;
> +}
> +
> static bool kvm_arch_setup_async_pf(struct kvm_vcpu *vcpu, gpa_t cr2_or_gpa,
> gfn_t gfn)
> {
> struct kvm_arch_async_pf arch;
>
> - arch.token = (vcpu->arch.apf.id++ << 12) | vcpu->vcpu_id;
> + arch.token = alloc_apf_token(vcpu);
> arch.gfn = gfn;
> arch.direct_map = vcpu->arch.mmu->direct_map;
> arch.cr3 = vcpu->arch.mmu->get_guest_pgd(vcpu);
Queued, thanks.
Paolo
next prev parent reply other threads:[~2022-02-22 8:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-22 3:12 Liang Zhang
2022-02-22 8:38 ` Paolo Bonzini [this message]
2022-03-10 3:34 ` Xinlong Lin
2022-03-10 3:42 ` zhangliang (AG)
2022-03-10 5:09 ` Xinlong Lin
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=6b5b8f01-6676-e7e4-d6d6-55c69f99a86d@redhat.com \
--to=pbonzini@redhat.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=wangzhigang17@huawei.com \
--cc=wanpengli@tencent.com \
--cc=x86@kernel.org \
--cc=zhangliang5@huawei.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
all inboxes | Powered by JetHome®