From: Oliver Upton <oupton@kernel.org>
To: Marc Zyngier <maz@kernel.org>, Karl Mehltretter <kmehltretter@gmail.com>
Cc: Oliver Upton <oupton@kernel.org>,
Fuad Tabba <fuad.tabba@linux.dev>,
Joey Gouly <joey.gouly@arm.com>,
Steffen Eiden <seiden@linux.ibm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v2] KVM: arm64: GICv2: Don't WARN on out-of-range GICV_DIR INTID
Date: Wed, 12 Aug 2026 23:49:43 -0700 [thread overview]
Message-ID: <178660378177.666424.79190290228047804.b4-ty@kernel.org> (raw)
In-Reply-To: <20260726174803.5880-1-kmehltretter@gmail.com>
On Sun, 26 Jul 2026 19:48:03 +0200, Karl Mehltretter wrote:
> 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.
>
> [...]
Applied to next, thanks!
[1/1] KVM: arm64: GICv2: Don't WARN on out-of-range GICV_DIR INTID
https://git.kernel.org/kvmarm/kvmarm/c/c6d9c8ac6521
--
Best,
Oliver
prev parent reply other threads:[~2026-08-13 6:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-26 17:48 Karl Mehltretter
2026-08-13 6:49 ` Oliver Upton [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=178660378177.666424.79190290228047804.b4-ty@kernel.org \
--to=oupton@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=fuad.tabba@linux.dev \
--cc=joey.gouly@arm.com \
--cc=kmehltretter@gmail.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=seiden@linux.ibm.com \
--cc=stable@vger.kernel.org \
--cc=suzuki.poulose@arm.com \
--cc=will@kernel.org \
--cc=yuzenghui@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®