diff options
| author | Michael Mueller <mimu@linux.vnet.ibm.com> | 2017-07-06 14:22:20 +0200 |
|---|---|---|
| committer | Christian Borntraeger <borntraeger@de.ibm.com> | 2017-11-09 09:49:48 +0100 |
| commit | 4dd6f17eb913d3d23dd6c07950627ac2c3068dca (patch) | |
| tree | e5221aa0838c34f9a29eb8d0368e71a03d2f4261 /Kbuild | |
| parent | ee739f4b216e9394281cf99e6d93c67bdf4a37d2 (diff) | |
KVM: s390: clear_io_irq() requests are not expected for adapter interrupts
There is a chance to delete not yet delivered I/O interrupts if an
exploiter uses the subsystem identification word 0x0000 while
processing a KVM_DEV_FLIC_CLEAR_IO_IRQ ioctl. -EINVAL will be returned
now instead in that case.
Classic interrupts will always have bit 0x10000 set in the schid while
adapter interrupts have a zero schid. The clear_io_irq interface is
only useful for classic interrupts (as adapter interrupts belong to
many devices). Let's make this interface more strict and forbid a schid
of 0.
Signed-off-by: Michael Mueller <mimu@linux.vnet.ibm.com>
Reviewed-by: Halil Pasic <pasic@linux.vnet.ibm.com>
Reviewed-by: Christian Borntraeger <borntraeger@de.ibm.com>
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
Diffstat (limited to 'Kbuild')
0 files changed, 0 insertions, 0 deletions