From: Paolo Bonzini <pbonzini@redhat.com>
To: David Woodhouse <dwmw2@infradead.org>, kvm <kvm@vger.kernel.org>
Cc: Sean Christopherson <seanjc@google.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Wanpeng Li <wanpengli@tencent.com>,
Jim Mattson <jmattson@google.com>, JoergRoedel <joro@8bytes.org>,
mtosatti <mtosatti@redhat.com>
Subject: Re: [PATCH] KVM: x86/xen: Fix kvm_xen_has_interrupt() sleeping in kvm_vcpu_block()
Date: Mon, 25 Oct 2021 15:10:28 +0200 [thread overview]
Message-ID: <83ac5bed-d613-28b3-4482-794bdd49abeb@redhat.com> (raw)
In-Reply-To: <168bf8c689561da904e48e2ff5ae4713eaef9e2d.camel@infradead.org>
On 23/10/21 21:47, David Woodhouse wrote:
> From: David Woodhouse <dwmw@amazon.co.uk>
>
> In kvm_vcpu_block, the current task is set to TASK_INTERRUPTIBLE before
> making a final check whether the vCPU should be woken from HLT by any
> incoming interrupt.
>
> This is a problem for the get_user() in __kvm_xen_has_interrupt(), which
> really shouldn't be sleeping when the task state has already been set.
> I think it's actually harmless as it would just manifest itself as a
> spurious wakeup, but it's causing a debug warning:
>
> [ 230.963649] do not call blocking ops when !TASK_RUNNING; state=1 set at [<00000000b6bcdbc9>] prepare_to_swait_exclusive+0x30/0x80
>
> Fix the warning by turning it into an *explicit* spurious wakeup. When
> invoked with !task_is_running(current) (and we might as well add
> in_atomic() there while we're at it), just return 1 to indicate that
> an IRQ is pending, which will cause a wakeup and then something will
> call it again in a context that *can* sleep so it can fault the page
> back in.
>
> Cc: stable@vger.kernel.org
> Fixes: 40da8ccd724f ("KVM: x86/xen: Add event channel interrupt vector upcall")
> Signed-off-by: David Woodhouse <dwmw@amazon.co.uk>
>
> ---
> arch/x86/kvm/xen.c | 27 ++++++++++++++++++++++-----
> 1 file changed, 22 insertions(+), 5 deletions(-)
>
> diff --git a/arch/x86/kvm/xen.c b/arch/x86/kvm/xen.c
> index 9ea9c3dabe37..8f62baebd028 100644
> --- a/arch/x86/kvm/xen.c
> +++ b/arch/x86/kvm/xen.c
> @@ -190,6 +190,7 @@ void kvm_xen_update_runstate_guest(struct kvm_vcpu *v, int state)
>
> int __kvm_xen_has_interrupt(struct kvm_vcpu *v)
> {
> + int err;
> u8 rc = 0;
>
> /*
> @@ -216,13 +217,29 @@ int __kvm_xen_has_interrupt(struct kvm_vcpu *v)
> if (likely(slots->generation == ghc->generation &&
> !kvm_is_error_hva(ghc->hva) && ghc->memslot)) {
> /* Fast path */
> - __get_user(rc, (u8 __user *)ghc->hva + offset);
> - } else {
> - /* Slow path */
> - kvm_read_guest_offset_cached(v->kvm, ghc, &rc, offset,
> - sizeof(rc));
> + pagefault_disable();
> + err = __get_user(rc, (u8 __user *)ghc->hva + offset);
> + pagefault_enable();
> + if (!err)
> + return rc;
> }
>
> + /* Slow path */
> +
> + /*
> + * This function gets called from kvm_vcpu_block() after setting the
> + * task to TASK_INTERRUPTIBLE, to see if it needs to wake immediately
> + * from a HLT. So we really mustn't sleep. If the page ended up absent
> + * at that point, just return 1 in order to trigger an immediate wake,
> + * and we'll end up getting called again from a context where we *can*
> + * fault in the page and wait for it.
> + */
> + if (in_atomic() || !task_is_running(current))
> + return 1;
> +
> + kvm_read_guest_offset_cached(v->kvm, ghc, &rc, offset,
> + sizeof(rc));
> +
> return rc;
> }
>
>
>
Queued, thanks.
Paolo
prev parent reply other threads:[~2021-10-25 13:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-23 19:47 [PATCH] KVM: x86/xen: Fix kvm_xen_has_interrupt() sleeping in kvm_vcpu_block() David Woodhouse
2021-10-25 11:28 ` Vitaly Kuznetsov
2021-10-25 13:18 ` David Woodhouse
2021-10-25 13:10 ` 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=83ac5bed-d613-28b3-4482-794bdd49abeb@redhat.com \
--to=pbonzini@redhat.com \
--cc=dwmw2@infradead.org \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=seanjc@google.com \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.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