[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <YyG2H8PbJjehAwch@google.com>
Date: Wed, 14 Sep 2022 12:08:15 +0100
From: Oliver Upton <oliver.upton@...ux.dev>
To: Zenghui Yu <yuzenghui@...wei.com>
Cc: kvmarm@...ts.cs.columbia.edu, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, maz@...nel.org, james.morse@....com,
alexandru.elisei@....com, suzuki.poulose@....com,
catalin.marinas@....com, will@...nel.org,
wanghaibin.wang@...wei.com, pbonzini@...hat.com
Subject: Re: [PATCH] KVM: arm64: Use kmemleak_free_part_phys() to unregister
hyp_mem_base
On Thu, Sep 08, 2022 at 09:06:59PM +0800, Zenghui Yu wrote:
> With commit 0c24e061196c ("mm: kmemleak: add rbtree and store physical
> address for objects allocated with PA"), kmemleak started to put the
> objects allocated with physical address onto object_phys_tree_root tree.
> The kmemleak_free_part() therefore no longer worked as expected on
> physically allocated objects (hyp_mem_base in this case) as it attempted to
> search and remove things in object_tree_root tree.
>
> Fix it by using kmemleak_free_part_phys() to unregister hyp_mem_base. This
> fixes an immediate crash when booting a KVM host in protected mode with
> kmemleak enabled.
>
> Signed-off-by: Zenghui Yu <yuzenghui@...wei.com>
Reviewed-by: Oliver Upton <oliver.upton@...ux.dev>
Marc or Paolo, do one of you want to pick this patch up? Looks like a
good fix.
--
Thanks,
Oliver
Powered by blists - more mailing lists