arm64: Enforce BBM for huge IO/VMAP mappings
authorWill Deacon <will.deacon@arm.com>
Wed, 21 Feb 2018 12:59:27 +0000 (12:59 +0000)
committerCatalin Marinas <catalin.marinas@arm.com>
Thu, 22 Feb 2018 11:25:53 +0000 (11:25 +0000)
commit15122ee2c515a253b0c66a3e618bc7ebe35105eb
tree930c790bb615babec3527f85fdbbec6628cf938d
parent0331365edb1d6ccd6ae68b1038111da85d4c68d1
arm64: Enforce BBM for huge IO/VMAP mappings

ioremap_page_range doesn't honour break-before-make and attempts to put
down huge mappings (using p*d_set_huge) over the top of pre-existing
table entries. This leads to us leaking page table memory and also gives
rise to TLB conflicts and spurious aborts, which have been seen in
practice on Cortex-A75.

Until this has been resolved, refuse to put block mappings when the
existing entry is found to be present.

Fixes: 324420bf91f60 ("arm64: add support for ioremap() block mappings")
Reported-by: Hanjun Guo <hanjun.guo@linaro.org>
Reported-by: Lei Li <lious.lilei@hisilicon.com>
Acked-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Will Deacon <will.deacon@arm.com>
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
arch/arm64/mm/mmu.c