From: Paolo Bonzini <pbonzini@redhat.com>
To: "Radim Krčmář" <rkrcmar@redhat.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
stable@vger.kernel.org, Dmitry Vyukov <dvyukov@google.com>,
Steve Rutherford <srutherford@google.com>
Subject: Re: [PATCH] KVM: x86: check for pic and ioapic presence before use
Date: Thu, 24 Nov 2016 11:34:46 -0500 (EST) [thread overview]
Message-ID: <2119448151.1732997.1480005286539.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20161124124206.GA16974@potion>
> Oops, I wrote the race with wrong IOCTL -- it should be KVM_IRQ_LINE.
>
> 1) set KVM_CAP_SPLIT_IRQCHIP (unlocks KVM_IRQ_LINE)
> a) call KVM_CREATE_IRQCHIP (creates routes while !kvm->arch.vpic)
> b) concurrently call KVM_IRQ_LINE for PIO routes (dereferences NULL)
>
> The problem is that we use pic_in_kernel() as irqchip_in_kernel(), so it
> cannot be set before we set up routes, but we then cannot reject routes
> when pic is not in use. The best effort is to do this for pic routes in
> kvm_set_routing_entry():
>
> // initialization is the only place where pic_in_kernel() !=
> ioapic_in_kernel()
> if (!pic_in_kernel(kvm) && !ioapic_in_kernel(kvm))
> goto out;
>
> and similar for ioapic routes:
>
> if (!ioapic_in_kernel(kvm))
> goto out;
>
> I think it would work if we forbade KVM_CREATE_IRQCHIP after
> KVM_CAP_SPLIT_IRQCHIP (which we want to do anyway).
Yeah, definitely.
> And adding a new
> variable for irqchip_in_kernel() would allow us to make the pic
> condition reasonabled.
Or change kvm->arch.irqchip_split to an enum.
> I'll do something like that for 4.10, but the current patch is better
> suited for stable.
>
> Would fixing the comment be enough?
Yes, fine!
> Do you want the following hunk already in 4.9?
>
> diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
> index 6f9c9ad13f88..dbed51045c37 100644
> --- a/arch/x86/kvm/x86.c
> +++ b/arch/x86/kvm/x86.c
> @@ -3901,7 +3901,7 @@ long kvm_arch_vm_ioctl(struct file *filp,
>
> mutex_lock(&kvm->lock);
> r = -EEXIST;
> - if (kvm->arch.vpic)
> + if (irqchip_in_kernel(kvm))
> goto create_irqchip_unlock;
> r = -EINVAL;
> if (kvm->created_vcpus)
No, it's unnecessary.
Paolo
next prev parent reply other threads:[~2016-11-24 16:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 20:25 [PATCH] KVM: x86: check for pic and ioapic presence before use Radim Krčmář
2016-11-23 21:58 ` Paolo Bonzini
2016-11-24 12:42 ` Radim Krčmář
2016-11-24 16:34 ` Paolo Bonzini [this message]
2016-12-20 11:59 ` Wanpeng Li
2016-12-21 12:44 ` Radim Krčmář
2016-12-22 9:56 ` Wanpeng Li
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=2119448151.1732997.1480005286539.JavaMail.zimbra@redhat.com \
--to=pbonzini@redhat.com \
--cc=dvyukov@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rkrcmar@redhat.com \
--cc=srutherford@google.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).