From: Alex Williamson <alex.williamson-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Li Zefan <lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
Cc: Marcelo Tosatti
<mtosatti-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
Gleb Natapov <gleb-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
kvm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Davide Libenzi <davidel-AhlLAIvw+VEjIGhXcJzhZg@public.gmane.org>,
LKML <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Cgroups <cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Gregory Haskins
<ghaskins-Et1tbQHTxzrQT0dZR+AlfA@public.gmane.org>,
"Kirill A. Shutemov"
<kirill-oKw7cIdHH8eLwutG50LtGA@public.gmane.org>
Subject: Re: [RFC][PATCH] kvm: fix a race when closing irq eventfd
Date: Sun, 17 Feb 2013 21:02:47 -0700 [thread overview]
Message-ID: <1361160167.2801.12.camel@bling.home> (raw)
In-Reply-To: <51219C57.7080809-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
On Mon, 2013-02-18 at 11:13 +0800, Li Zefan wrote:
> While trying to fix a race when closing cgroup eventfd, I took a look
> at how kvm deals with this problem, and I found it doesn't.
>
> I may be wrong, as I don't know kvm code, so correct me if I'm.
>
> /*
> * Race-free decouple logic (ordering is critical)
> */
> static void
> irqfd_shutdown(struct work_struct *work)
>
> I don't think it's race-free!
>
> static int
> irqfd_wakeup(wait_queue_t *wait, unsigned mode, int sync, void *key)
> {
> ...
> * We cannot race against the irqfd going away since the
> * other side is required to acquire wqh->lock, which we hold
> */
> if (irqfd_is_active(irqfd))
> irqfd_deactivate(irqfd);
> }
>
> In kvm_irqfd_deassign() and kvm_irqfd_release() where irqfds are freed,
> wqh->lock is not acquired!
>
> So here is the race:
>
> CPU0 CPU1
> ----------------------------------- ---------------------------------
> kvm_irqfd_release()
> spin_lock(kvm->irqfds.lock);
> ...
> irqfd_deactivate(irqfd);
> list_del_init(&irqfd->list);
> spin_unlock(kvm->irqfd.lock);
> ...
> close(eventfd)
> irqfd_wakeup();
irqfd_wakeup is assumed to be called with wqh->lock held
> irqfd_shutdown();
eventfd_ctx_remove_wait_queue has to acquire wqh->lock to complete or
else irqfd_shutdown never makes it to the kfree. So in your scenario
this cpu0 spins here until cpu1 completes.
> remove_waitqueue(irqfd->wait);
> kfree(irqfd);
> spin_lock(kvm->irqfd.lock);
> if (!list_empty(&irqfd->list))
We don't take this branch because we already did list_del_init above,
which makes irqfd->list empty.
> irqfd_deactivate(irqfd);
> list_del_init(&irqfd->list);
> spin_unlock(kvm->irqfd.lock);
>
> Look, we're accessing irqfd though it has already been freed!
Unless the irqfd_wakeup path isn't acquiring wqh->lock, it looks
race-free to me. Thanks,
Alex
next prev parent reply other threads:[~2013-02-18 4:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 3:13 [RFC][PATCH] kvm: fix a race when closing irq eventfd Li Zefan
[not found] ` <51219C57.7080809-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2013-02-18 4:02 ` Alex Williamson [this message]
2013-02-18 4:09 ` Li Zefan
2013-02-18 4:25 ` Alex Williamson
[not found] ` <5121A971.7000604-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2013-02-18 4:31 ` Li Zefan
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=1361160167.2801.12.camel@bling.home \
--to=alex.williamson-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=davidel-AhlLAIvw+VEjIGhXcJzhZg@public.gmane.org \
--cc=ghaskins-Et1tbQHTxzrQT0dZR+AlfA@public.gmane.org \
--cc=gleb-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=kirill-oKw7cIdHH8eLwutG50LtGA@public.gmane.org \
--cc=kvm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org \
--cc=mtosatti-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.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