linux-kernel - Re: [PATCH v2] KVM: arm64: Move bundling vLPI and vSGI to vgic_supports_direct

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <175382415249.3325682.6984441451099105450.b4-ty@linux.dev>
Date: Tue, 29 Jul 2025 14:23:16 -0700
From: Oliver Upton <oliver.upton@...ux.dev>
To: Marc Zyngier <maz@...nel.org>,
	Raghavendra Rao Ananta <rananta@...gle.com>
Cc: Oliver Upton <oliver.upton@...ux.dev>,
	linux-arm-kernel@...ts.infradead.org,
	kvmarm@...ts.linux.dev,
	linux-kernel@...r.kernel.org,
	kvm@...r.kernel.org
Subject: Re: [PATCH v2] KVM: arm64: Move bundling vLPI and vSGI to vgic_supports_direct_msis()

On Tue, 29 Jul 2025 21:06:44 +0000, Raghavendra Rao Ananta wrote:
> Commit <c652887a9288> ("KVM: arm64: vgic-v3: Allow userspace to write
> GICD_TYPER2.nASSGIcap") bundles the vLPIs and vSGIs behind the
> GICD_TYPER2.nASSGIcap field. While the vGIC v4 initialization and
> teardown is handled correctly, it erroneously left out the cases when
> KVM sets/unset vGIC v4 forwarding, which leads to a kernel panic of the
> following nature:
> 
> [...]

Massaged the changelog a bit. Applied to fixes, thanks!

[1/1] KVM: arm64: Move bundling vLPI and vSGI to vgic_supports_direct_msis()
      https://git.kernel.org/kvmarm/kvmarm/c/7b8346bd9fce

--
Best,
Oliver