Alex Williamson 3be3a074cf vfio-pci: Don't use device_lock around AER interrupt setup ... device_lock is much too prone to lockups. For instance if we have a pending .remove then device_lock is already held. If userspace attempts to modify AER signaling after that point, a deadlock occurs. eventfd setup/teardown is already protected in vfio with the igate mutex. AER is not a high performance interrupt, so we can also use the same mutex to protect signaling versus setup races. Signed-off-by: Alex Williamson <alex.williamson@redhat.com>		2014-01-14 16:12:55 -07:00
..
Kconfig	drivers/vfio: remove depends on CONFIG_EXPERIMENTAL	2013-02-24 09:59:44 -07:00
Makefile
vfio_pci_config.c	vfio-pci: Test for extended config space	2013-09-04 10:58:52 -06:00
vfio_pci_intrs.c	vfio-pci: Don't use device_lock around AER interrupt setup	2014-01-14 16:12:55 -07:00
vfio_pci_private.h	VFIO-AER: Vfio-pci driver changes for supporting AER	2013-03-11 09:31:22 -06:00
vfio_pci_rdwr.c	vfio-pci: Add support for VGA region access	2013-02-18 10:11:13 -07:00
vfio_pci.c	vfio-pci: Don't use device_lock around AER interrupt setup	2014-01-14 16:12:55 -07:00