linux-kernel - Re: linux-next: manual merge of the arm64 tree with the origin tree

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: <a8f3a715-6e24-4f79-8300-d8f89430bebe@sirena.org.uk>
Date: Mon, 26 Jan 2026 22:49:45 +0000
From: Mark Brown <broonie@...nel.org>
To: Marc Zyngier <maz@...nel.org>
Cc: Catalin Marinas <catalin.marinas@....com>,
	Will Deacon <will@...nel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linux Next Mailing List <linux-next@...r.kernel.org>,
	Oliver Upton <oupton@...nel.org>,
	Paolo Bonzini <pbonzini@...hat.com>
Subject: Re: linux-next: manual merge of the arm64 tree with the origin tree

On Mon, Jan 26, 2026 at 03:39:39PM +0000, Marc Zyngier wrote:

> Keeping the version from Linus' tree doesn't work, as
> kvm_pan_patch_el2_entry() references CONFIG_ARM64_PAN, which is
> removed by 018a231b0260e ("arm64: Unconditionally enable PAN
> support").

I was expecting some fixup to be required in there, yes - at a first
glance the VHE based decisions looked like they'd still want to be made,
though I didn't check in detail.

> So the arm64 version should be the correct one.

I've applied a fixup doing that.

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