From: christoffer.dall@linaro.org (Christoffer Dall)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] KVM: arm64: vgic-its: Plug race in vgic_put_irq
Date: Tue, 9 Aug 2016 12:20:19 +0200 [thread overview]
Message-ID: <20160809102019.GC9175@cbox> (raw)
In-Reply-To: <ff8d6b98-a013-5292-af35-8fd97ec54700@arm.com>
On Mon, Aug 08, 2016 at 12:20:14PM +0100, Andre Przywara wrote:
> Hi,
>
> On 03/08/16 17:13, Christoffer Dall wrote:
> > Right now the following sequence of events can happen:
> >
> > 1. Thread X calls vgic_put_irq
> > 2. Thread Y calls vgic_add_lpi
> > 3. Thread Y gets lpi_list_lock
> > 4. Thread X drops the ref count to 0 and blocks on lpi_list_lock
> > 5. Thread Y finds the irq via the lpi_list_lock, raises the ref
> > count to 1, and release the lpi_list_lock.
> > 6. Thread X proceeds and frees the irq.
> >
> > Avoid this by holding the spinlock around the kref_put.
> >
> > Signed-off-by: Christoffer Dall <christoffer.dall@linaro.org>
> > ---
> > virt/kvm/arm/vgic/vgic.c | 20 ++++++++++----------
> > 1 file changed, 10 insertions(+), 10 deletions(-)
> >
> > diff --git a/virt/kvm/arm/vgic/vgic.c b/virt/kvm/arm/vgic/vgic.c
> > index e7aeac7..fb8c0ab 100644
> > --- a/virt/kvm/arm/vgic/vgic.c
> > +++ b/virt/kvm/arm/vgic/vgic.c
> > @@ -117,22 +117,22 @@ static void vgic_irq_release(struct kref *ref)
> >
> > void vgic_put_irq(struct kvm *kvm, struct vgic_irq *irq)
> > {
> > - struct vgic_dist *dist;
> > + struct vgic_dist *dist = &kvm->arch.vgic;
> >
> > if (irq->intid < VGIC_MIN_LPI)
> > return;
> >
> > - if (!kref_put(&irq->refcount, vgic_irq_release))
> > - return;
> > -
> > - dist = &kvm->arch.vgic;
> > -
> > spin_lock(&dist->lpi_list_lock);
> > - list_del(&irq->lpi_list);
> > - dist->lpi_list_count--;
> > - spin_unlock(&dist->lpi_list_lock);
> > + if (!kref_put(&irq->refcount, vgic_irq_release)) {
> > + spin_unlock(&dist->lpi_list_lock);
> > + return;
> > + } else {
>
> Just a nit, I guess, but we don't need this "else" since the if-branch
> always returns?
>
correct, I can change that.
> > + list_del(&irq->lpi_list);
> > + dist->lpi_list_count--;
> > + spin_unlock(&dist->lpi_list_lock);
> >
> > - kfree(irq);
> > + kfree(irq);
> > + }
> > }
> >
> > /**
> >
>
> Otherwise:
>
> Reviewed-by: Andre Przywara <andre.przywara@arm.com>
>
Thanks.
-Christoffer
next prev parent reply other threads:[~2016-08-09 10:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-03 16:13 [PATCH 0/3] KVM: arm64: vgic-its fixes Christoffer Dall
2016-08-03 16:13 ` [PATCH v2 1/3] KVM: arm64: vgic-its: Handle errors from vgic_add_lpi Christoffer Dall
2016-08-08 11:00 ` Andre Przywara
2016-08-09 10:09 ` Christoffer Dall
2016-08-03 16:13 ` [PATCH 2/3] KVM: arm64: vgic-its: Plug race in vgic_put_irq Christoffer Dall
2016-08-08 11:20 ` Andre Przywara
2016-08-09 10:20 ` Christoffer Dall [this message]
2016-08-03 16:13 ` [PATCH 3/3] KVM: arm64: vgic-its: Make updates to propbaser/pendbaser atomic Christoffer Dall
2016-08-08 13:30 ` Andre Przywara
2016-08-09 10:30 ` Christoffer Dall
2016-08-09 10:43 ` Christoffer Dall
2016-08-09 11:19 ` Andre Przywara
2016-08-09 11:56 ` Christoffer Dall
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=20160809102019.GC9175@cbox \
--to=christoffer.dall@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).