diff options
author | 2015-06-17 14:43:35 +0100 | |
---|---|---|
committer | 2015-06-17 15:18:59 +0100 | |
commit | 4839ddc27b7212ec58874f62c97da7400c8523be (patch) | |
tree | 5278f3b4580f010ed2ca9692cefd25d1ab591123 /tools/perf/scripts/python/call-graph-from-postgresql.py | |
parent | arm/arm64: KVM: vgic: Do not save GICH_HCR / ICH_HCR_EL2 (diff) | |
download | wireguard-linux-4839ddc27b7212ec58874f62c97da7400c8523be.tar.xz wireguard-linux-4839ddc27b7212ec58874f62c97da7400c8523be.zip |
KVM: arm/arm64: vgic: Avoid injecting reserved IRQ numbers
Commit fd1d0ddf2ae9 (KVM: arm/arm64: check IRQ number on userland
injection) rightly limited the range of interrupts userspace can
inject in a guest, but failed to consider the (unlikely) case where
a guest is configured with 1024 interrupts.
In this case, interrupts ranging from 1020 to 1023 are unuseable,
as they have a special meaning for the GIC CPU interface.
Make sure that these number cannot be used as an IRQ. Also delete
a redundant (and similarily buggy) check in kvm_set_irq.
Reported-by: Peter Maydell <peter.maydell@linaro.org>
Cc: Andre Przywara <andre.przywara@arm.com>
Cc: <stable@vger.kernel.org> # 4.1, 4.0, 3.19, 3.18
Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions