diff options
| author | 2022-09-08 21:06:59 +0800 | |
|---|---|---|
| committer | 2022-09-19 17:59:48 +0100 | |
| commit | 522c9a64c7049f50c7b1299741c13fac3f231cd4 (patch) | |
| tree | c8756f0c8ea83b7bc846ca71dc8928d82e5542b3 /tools/scripts/ssh:/git@git.zx2c4.com/git: | |
| parent | Linux 6.0-rc2 (diff) | |
| download | linux-dev-522c9a64c7049f50c7b1299741c13fac3f231cd4.tar.xz linux-dev-522c9a64c7049f50c7b1299741c13fac3f231cd4.zip | |
KVM: arm64: Use kmemleak_free_part_phys() to unregister hyp_mem_base
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@huawei.com>
Acked-by: Catalin Marinas <catalin.marinas@arm.com>
Reviewed-by: Oliver Upton <oliver.upton@linux.dev>
Signed-off-by: Marc Zyngier <maz@kernel.org>
Link: https://lore.kernel.org/r/20220908130659.2021-1-yuzenghui@huawei.com
Diffstat (limited to 'tools/scripts/ssh:/git@git.zx2c4.com/git:')
0 files changed, 0 insertions, 0 deletions
