xen/pciback: For XEN_PCI_OP_disable_msi[|x] only disable if device has MSI(X) enabled.
authorKonrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Wed, 1 Apr 2015 14:49:47 +0000 (10:49 -0400)
committerZefan Li <lizefan@huawei.com>
Wed, 26 Oct 2016 15:15:40 +0000 (23:15 +0800)
commit7e8c20ac766e4403b9b5277403112b77f916c2cf
tree115df6acc66c4928d57c561e0de1ac194e25f9ec
parent073a5ac1cb93623e71cda2510929dcffd0b9554b
xen/pciback: For XEN_PCI_OP_disable_msi[|x] only disable if device has MSI(X) enabled.

commit 7cfb905b9638982862f0331b36ccaaca5d383b49 upstream.

Otherwise just continue on, returning the same values as
previously (return of 0, and op->result has the PIRQ value).

This does not change the behavior of XEN_PCI_OP_disable_msi[|x].

The pci_disable_msi or pci_disable_msix have the checks for
msi_enabled or msix_enabled so they will error out immediately.

However the guest can still call these operations and cause
us to disable the 'ack_intr'. That means the backend IRQ handler
for the legacy interrupt will not respond to interrupts anymore.

This will lead to (if the device is causing an interrupt storm)
for the Linux generic code to disable the interrupt line.

Naturally this will only happen if the device in question
is plugged in on the motherboard on shared level interrupt GSI.

This is part of XSA-157

Reviewed-by: David Vrabel <david.vrabel@citrix.com>
Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Signed-off-by: Zefan Li <lizefan@huawei.com>
drivers/xen/xen-pciback/pciback_ops.c