linux-kernel - Re: [PATCH] KVM: arm64: gic-v3: Only set ICH

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <0a381733-6b5d-4aa0-bb3d-15a98a665c1c@sirena.org.uk>
Date: Tue, 21 Oct 2025 12:39:47 +0100
From: Mark Brown <broonie@...nel.org>
To: Sean Christopherson <seanjc@...gle.com>
Cc: Sascha Bischoff <Sascha.Bischoff@....com>,
	"linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org>,
	"kvmarm@...ts.linux.dev" <kvmarm@...ts.linux.dev>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"kvm@...r.kernel.org" <kvm@...r.kernel.org>, nd <nd@....com>,
	"maz@...nel.org" <maz@...nel.org>,
	"oliver.upton@...ux.dev" <oliver.upton@...ux.dev>,
	Joey Gouly <Joey.Gouly@....com>,
	Suzuki Poulose <Suzuki.Poulose@....com>,
	"yuzenghui@...wei.com" <yuzenghui@...wei.com>,
	Paolo Bonzini <pbonzini@...hat.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Aishwarya.TCV@....com
Subject: Re: [PATCH] KVM: arm64: gic-v3: Only set ICH_HCR traps for v2-on-v3
 or v3 guests

On Mon, Oct 20, 2025 at 05:50:02PM -0700, Sean Christopherson wrote:
> On Tue, Oct 21, 2025, Mark Brown wrote:

> > hours before Paolo sent his pull request to Linus, so there was no
> > opportunity for it to be picked up.  As I've previously suggested it
> > does seem like it would be a good idea to include the fixes branches for
> > the KVM arch trees in -next (s390 is there, but I don't see the others),

> FWIW, "kvm-x86 fixes" is in -next (unless I've screwed up recently), it just gets
> routed in via "kvm-x86 next" via an octopus merge.

Ah, excellent - I was just checking for separate fixes branches.  It
would still be nice to have your fixes branch in -next directly so that
it can be included in pending-fixes (which merges only fixes branches),
that does get some specific coverage so we notice if there's any
dependencies on -next changes that wasn't noticed (it exists because
there were a few issues with that a while back).  It's very rare for it
to find anything but it doesn't hurt.

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)