summaryrefslogtreecommitdiffstats
path: root/security/integrity
diff options
context:
space:
mode:
authorMarcelo Tosatti2009-05-07 22:55:13 +0200
committerAvi Kivity2009-06-10 10:48:53 +0200
commit547de29e5b1662deb05b5f90917902dc0e9ac182 (patch)
treec8c8d913729f4577251d3bceb9fe52b676f7a5a8 /security/integrity
parentKVM: use smp_send_reschedule in kvm_vcpu_kick (diff)
downloadkernel-qcow2-linux-547de29e5b1662deb05b5f90917902dc0e9ac182.tar.gz
kernel-qcow2-linux-547de29e5b1662deb05b5f90917902dc0e9ac182.tar.xz
kernel-qcow2-linux-547de29e5b1662deb05b5f90917902dc0e9ac182.zip
KVM: protect assigned dev workqueue, int handler and irq acker
kvm_assigned_dev_ack_irq is vulnerable to a race condition with the interrupt handler function. It does: if (dev->host_irq_disabled) { enable_irq(dev->host_irq); dev->host_irq_disabled = false; } If an interrupt triggers before the host->dev_irq_disabled assignment, it will disable the interrupt and set dev->host_irq_disabled to true. On return to kvm_assigned_dev_ack_irq, dev->host_irq_disabled is set to false, and the next kvm_assigned_dev_ack_irq call will fail to reenable it. Other than that, having the interrupt handler and work handlers run in parallel sounds like asking for trouble (could not spot any obvious problem, but better not have to, its fragile). CC: sheng.yang@intel.com Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com> Signed-off-by: Avi Kivity <avi@redhat.com>
Diffstat (limited to 'security/integrity')
0 files changed, 0 insertions, 0 deletions