[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <175793328164.659173.8404797812390171241.b4-ty@kernel.org>
Date: Mon, 15 Sep 2025 11:49:14 +0100
From: Marc Zyngier <maz@...nel.org>
To: Oliver Upton <oliver.upton@...ux.dev>,
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>,
James Clark <james.clark@...aro.org>,
Yingchao Deng <yingchao.deng@....qualcomm.com>
Cc: linux-arm-kernel@...ts.infradead.org,
kvmarm@...ts.linux.dev,
linux-kernel@...r.kernel.org,
quic_yingdeng@...cinc.com,
jinlong.mao@....qualcomm.com,
tingwei.zhang@....qualcomm.com
Subject: Re: [PATCH v2] KVM: arm64: Fix NULL pointer access issue
On Tue, 02 Sep 2025 11:48:25 +0800, Yingchao Deng wrote:
> When linux is booted in EL1, macro "host_data_ptr()" is a wrapper that
> resolves to "&per_cpu_ptr_nvhe_sym(kvm_host_data, cpu)",
> is_hyp_mode_available() return false during kvm_arm_init, the per-CPU base
> pointer __kvm_nvhe_kvm_arm_hyp_percpu_base[cpu] remains uninitialized.
> Consequently, any access via per_cpu_ptr_nvhe_sym(kvm_host_data, cpu)
> will result in a NULL pointer.
>
> [...]
Applied to next, thanks!
[1/1] KVM: arm64: Fix NULL pointer access issue
commit 27d2b47eef033f1fc6c0452dc1017e43dad5fe14
Cheers,
M.
--
Without deviation from the norm, progress is not possible.
Powered by blists - more mailing lists