linux-kernel - Re: [PATCH v2 0/1] KVM: arm64: Calculate hyp VA size only once

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: <176838788525.3448059.9914160373754507949.b4-ty@kernel.org>
Date: Wed, 14 Jan 2026 10:51:37 +0000
From: Marc Zyngier <maz@...nel.org>
To: kvmarm@...ts.linux.dev,
	Petteri Kangaslampi <pekangas@...gle.com>
Cc: Vincent Donnefort <vdonnefort@...gle.com>,
	Joey Gouly <joey.gouly@....com>,
	Suzuki K Poulose <suzuki.poulose@....com>,
	Zenghui Yu <yuzenghui@...wei.com>,
	Catalin Marinas <catalin.marinas@....com>,
	Will Deacon <will@...nel.org>,
	linux-arm-kernel@...ts.infradead.org,
	linux-kernel@...r.kernel.org,
	Oliver Upton <oupton@...nel.org>
Subject: Re: [PATCH v2 0/1] KVM: arm64: Calculate hyp VA size only once

On Tue, 13 Jan 2026 19:44:08 +0000, Petteri Kangaslampi wrote:
> All,
> 
> Here's a reworked fix to keep VA size calculations consistent between
> the MMU and layout initialization code paths.
> 
> Previously, if the kernel was configured with a VA size of less than
> 48 bits (like happens in our environment), the assumptions used to
> calculate hyp_physvirt_offset in kvm_compute_layout() and the code
> that determines the VA size used in the rest of the system (calculated
> in kvm_mmu_init()) would get out of sync. This could eventually result
> in mapping failures.
> 
> [...]

Applied to next, thanks!

[1/1] KVM: arm64: Calculate hyp VA size only once
      commit: 8e8eb10c107e67f22f87cd8c963d30ea73f04d5f

Cheers,

	M.
-- 
Without deviation from the norm, progress is not possible.