[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <165545408679.771055.5076080259874437048.b4-ty@kernel.org>
Date: Fri, 17 Jun 2022 09:21:31 +0100
From: Marc Zyngier <maz@...nel.org>
To: Suzuki K Poulose <suzuki.poulose@....com>,
Alexandru Elisei <alexandru.elisei@....com>,
linux-arm-kernel@...ts.infradead.org,
Catalin Marinas <catalin.marinas@....com>,
Quentin Perret <qperret@...gle.com>,
kvmarm@...ts.cs.columbia.edu, linux-kernel@...r.kernel.org,
James Morse <james.morse@....com>,
Will Deacon <will@...nel.org>
Cc: Mike Rapoport <rppt@...nel.org>, kernel-team@...roid.com
Subject: Re: [PATCH] KVM: arm64: Prevent kmemleak from accessing pKVM memory
On Thu, 16 Jun 2022 16:11:34 +0000, Quentin Perret wrote:
> Commit a7259df76702 ("memblock: make memblock_find_in_range method
> private") changed the API using which memory is reserved for the pKVM
> hypervisor. However, it seems that memblock_phys_alloc() differs
> from the original API in terms of kmemleak semantics -- the old one
> excluded the reserved regions from kmemleak scans when the new one
> doesn't seem to. Unfortunately, when protected KVM is enabled, all
> kernel accesses to pKVM-private memory result in a fatal exception,
> which can now happen because of kmemleak scans:
>
> [...]
Applied to fixes, thanks!
[1/1] KVM: arm64: Prevent kmemleak from accessing pKVM memory
commit: 9e5afa8a537f742bccc2cd91bc0bef4b6483ee98
Cheers,
M.
--
Marc Zyngier <maz@...nel.org>
Powered by blists - more mailing lists