linux-kernel - [KVM-RFC PATCH 0/2] irqfd: use POLLHUP notification for close()

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090602151135.29746.91320.stgit@dev.haskins.net>
Date:	Tue, 02 Jun 2009 11:15:28 -0400
From:	Gregory Haskins <ghaskins@...ell.com>
To:	kvm@...r.kernel.org
Cc:	linux-kernel@...r.kernel.org, avi@...hat.com,
	davidel@...ilserver.org, mst@...hat.com, paulmck@...ux.vnet.ibm.com
Subject: [KVM-RFC PATCH 0/2] irqfd: use POLLHUP notification for close()

(Applies to kvm.git/master:25deed73)

Please see the header for 2/2 for a description.  This patch series has
been fully tested and appears to be working correctly.  I have it as an RFC
for now because it needs Davide's official submission/SOB for patch 1/2, and
it should get some eyeballs/acks on my SRCU usage before going in.

I will submit the updated irqfd userspace which eschews the deassign() verb
since we can now just use the close(fd) method alone.  I will also address
the userspace review comments from Avi.

---

Davide Libenzi (1):
      eventfd: send POLLHUP on f_ops->release

Gregory Haskins (1):
      kvm: use POLLHUP to close an irqfd instead of an explicit ioctl

 fs/eventfd.c        |   10 +++
 include/linux/kvm.h |    2 -
 virt/kvm/eventfd.c  |  177 +++++++++++++++++++++++----------------------------
 virt/kvm/kvm_main.c |    3 +
 4 files changed, 90 insertions(+), 102 deletions(-)

-- 
Signature
--
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/