[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090604124807.10544.6071.stgit@dev.haskins.net>
Date: Thu, 04 Jun 2009 08:48:07 -0400
From: Gregory Haskins <ghaskins@...ell.com>
To: kvm@...r.kernel.org
Cc: linux-kernel@...r.kernel.org, avi@...hat.com,
davdel@...ilserver.org, mst@...hat.com, paulmck@...ux.vnet.ibm.com,
akpm@...ux-foundation.org
Subject: [KVM PATCH v2 1/2] Allow waiters to be notified about the eventfd
file* going away, and give
From: Davide Libenzi <davidel@...ilserver.org>
them a change to unregister from the wait queue. This is turn allows
eventfd users to use the eventfd file* w/out holding a live reference to
it.
After the eventfd user callbacks returns, any usage of the eventfd file*
should be dropped. The eventfd user callback can acquire sleepy locks
since it is invoked lockless.
This is a feature, needed by KVM to avoid an awkward workaround when using
eventdf.
[gmh: pulled from -mmotm for inclusion in kvm.git]
Signed-off-by: Davide Libenzi <davidel@...ilserver.org>
Tested-by: Gregory Haskins <ghaskins@...ell.com>
Signed-off-by: Andrew Morton <akpm@...ux-foundation.org>
Signed-off-by: Gregory Haskins <ghaskins@...ell.com>
---
fs/eventfd.c | 10 +++++++++-
1 files changed, 9 insertions(+), 1 deletions(-)
diff --git a/fs/eventfd.c b/fs/eventfd.c
index 3f0e197..72f5f8d 100644
--- a/fs/eventfd.c
+++ b/fs/eventfd.c
@@ -61,7 +61,15 @@ EXPORT_SYMBOL_GPL(eventfd_signal);
static int eventfd_release(struct inode *inode, struct file *file)
{
- kfree(file->private_data);
+ struct eventfd_ctx *ctx = file->private_data;
+
+ /*
+ * No need to hold the lock here, since we are on the file cleanup
+ * path and the ones still attached to the wait queue will be
+ * serialized by wake_up_locked_poll().
+ */
+ wake_up_locked_poll(&ctx->wqh, POLLHUP);
+ kfree(ctx);
return 0;
}
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists