linux-kernel - Re: KVM: x86/xen: Allow 'out of range' event channel ports in IRQ routing table.

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: <175079198224.513744.6336161745259606181.b4-ty@google.com>
Date: Tue, 24 Jun 2025 12:38:16 -0700
From: Sean Christopherson <seanjc@...gle.com>
To: Sean Christopherson <seanjc@...gle.com>, kvm@...r.kernel.org, 
	Ivan Orlov <iorlov@...zon.co.uk>, David Woodhouse <dwmw2@...radead.org>
Cc: Paul Durrant <paul@....org>, Paolo Bonzini <pbonzini@...hat.com>, 
	Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>, 
	Dave Hansen <dave.hansen@...ux.intel.com>, x86@...nel.org, 
	"H. Peter Anvin" <hpa@...or.com>, linux-kernel@...r.kernel.org
Subject: Re: KVM: x86/xen: Allow 'out of range' event channel ports in IRQ
 routing table.

On Thu, 08 May 2025 13:30:12 -0700, David Woodhouse wrote:
> To avoid imposing an ordering constraint on userspace, allow 'invalid'
> event channel targets to be configured in the IRQ routing table.
> 
> This is the same as accepting interrupts targeted at vCPUs which don't
> exist yet, which is already the case for both Xen event channels *and*
> for MSIs (which don't do any filtering of permitted APIC ID targets at
> all).
> 
> [...]

Applied to kvm-x86 fixes, thanks!

[1/1] KVM: x86/xen: Allow 'out of range' event channel ports in IRQ routing table.
      https://github.com/kvm-x86/linux/commit/a7f4dff21fd7

--
https://github.com/kvm-x86/kvm-unit-tests/tree/next