diff options
| author | Karl Mehltretter <kmehltretter@gmail.com> | 2026-07-26 19:48:03 +0200 |
|---|---|---|
| committer | Marc Zyngier <maz@kernel.org> | 2026-07-27 08:12:19 +0100 |
| commit | 751a956c75a5449e1769897f374094ea476ba1a1 (patch) | |
| tree | 8e1593947dec69def27a101e9312e02c319de0ce /scripts | |
| parent | 679d7201c1f09e37fa1c12ce28d84079c17fc87f (diff) | |
| download | linux-next-751a956c75a5449e1769897f374094ea476ba1a1.tar.gz linux-next-751a956c75a5449e1769897f374094ea476ba1a1.zip | |
KVM: arm64: GICv2: Don't WARN on out-of-range INTID writes to GICV_DIR
vgic_v2_deactivate() passes the INTID a guest wrote to GICV_DIR straight
to vgic_get_vcpu_irq(), and treats a failed lookup as a "can't happen"
condition with WARN_ON_ONCE().
The guest can make it happen at will, though: for any INTID outside of
the implemented SGI, PPI and SPI ranges the lookup returns NULL, since
GICv2 has no LPIs. A guest running with EOImode==1 writing such an INTID
to GICV_DIR triggers the WARN, and panics hosts running with
panic_on_warn.
Drop the WARN and ignore failed lookups.
Fixes: 255de897e7fb ("KVM: arm64: GICv2: Handle deactivation via GICV_DIR traps")
Cc: stable@vger.kernel.org
Suggested-by: Marc Zyngier <maz@kernel.org>
Signed-off-by: Karl Mehltretter <kmehltretter@gmail.com>
Link: https://patch.msgid.link/20260726174803.5880-1-kmehltretter@gmail.com
Signed-off-by: Marc Zyngier <maz@kernel.org>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions