From: Gregory Haskins <ghaskins@novell.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: kvm@vger.kernel.org, avi@redhat.com
Subject: Re: [KVM PATCH v5 3/4] KVM: Fix races in irqfd using new eventfd_kref_get interface
Date: Sun, 28 Jun 2009 08:53:22 -0400 [thread overview]
Message-ID: <4A4767C2.3010503@novell.com> (raw)
In-Reply-To: <20090628114846.GA11764@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1253 bytes --]
Michael S. Tsirkin wrote:
> On Thu, Jun 25, 2009 at 09:28:27AM -0400, Gregory Haskins wrote:
>
>> eventfd currently emits a POLLHUP wakeup on f_ops->release() to generate a
>> "release" callback. This lets eventfd clients know if the eventfd is about
>> to go away and is very useful particularly for in-kernel clients. However,
>> until recently it is not possible to use this feature of eventfd in a
>> race-free way. This patch utilizes a new eventfd interface to rectify
>> the problem.
>>
>> Note that one final race is known to exist: the slow-work thread may race
>> with module removal. We are currently working with slow-work upstream
>> to fix this issue as well. Since the code prior to this patch also
>> races with module_put(), we are not making anything worse, but rather
>> shifting the cause of the race. Once the slow-work code is patched we
>> will be fixing the last remaining issue.
>>
>
> By the way, why are we using slow-work here? Wouldn't a regular
> workqueue do just as well, with less code, and avoid the race?
>
>
I believe it will cause a problem if you do a "flush_work()" from inside
a work-item. I could be wrong, of course, but it looks like a recipe to
deadlock.
-Greg
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 266 bytes --]
next prev parent reply other threads:[~2009-06-28 12:53 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-25 13:28 [KVM PATCH v5 0/4] irqfd fixes and enhancements Gregory Haskins
2009-06-25 13:28 ` [KVM PATCH v5 1/4] kvm: prepare irqfd for having interrupts disabled during eventfd->release Gregory Haskins
2009-06-25 13:28 ` [KVM PATCH v5 2/4] eventfd - revised interface and cleanups (4th rev) Gregory Haskins
2009-06-25 13:28 ` [KVM PATCH v5 3/4] KVM: Fix races in irqfd using new eventfd_kref_get interface Gregory Haskins
2009-06-26 14:05 ` Gregory Haskins
2009-06-28 11:06 ` Michael S. Tsirkin
2009-06-28 12:50 ` Gregory Haskins
2009-06-28 13:18 ` Michael S. Tsirkin
2009-06-28 13:25 ` Avi Kivity
2009-06-28 11:48 ` Michael S. Tsirkin
2009-06-28 12:53 ` Gregory Haskins [this message]
2009-06-28 12:56 ` Michael S. Tsirkin
2009-06-28 12:57 ` Michael S. Tsirkin
2009-06-28 13:20 ` Michael S. Tsirkin
2009-06-28 16:28 ` Gregory Haskins
2009-06-28 19:07 ` Michael S. Tsirkin
2009-06-28 19:54 ` Gregory Haskins
2009-06-28 20:07 ` Michael S. Tsirkin
2009-06-28 20:17 ` Gregory Haskins
2009-06-28 16:25 ` Gregory Haskins
2009-06-25 13:28 ` [KVM PATCH v5 4/4] KVM: add irqfd DEASSIGN feature Gregory Haskins
2009-06-28 10:46 ` Michael S. Tsirkin
2009-06-28 12:39 ` Gregory Haskins
2009-06-25 13:59 ` [KVM PATCH v5 0/4] irqfd fixes and enhancements Gregory Haskins
2009-06-25 16:44 ` Davide Libenzi
2009-06-28 11:03 ` Avi Kivity
2009-06-28 12:59 ` Gregory Haskins
2009-06-28 13:40 ` Avi Kivity
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=4A4767C2.3010503@novell.com \
--to=ghaskins@novell.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.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