mm/memremap: avoid calling kasan_remove_zero_shadow() for device private memory
Subsystems (2)
PATCH 1/1 mm/memremap: avoid calling kasan_remove_zero_shadow() for device private memory
For device private memory, we do not create a linear mapping for the memory because the device memory is un-accessible. Thus we do not add kasan zero shadow for it. So it's unnecessary to do kasan_remove_zero_shadow() for it.
Signed-off-by Miaohe Lin <[email protected]>
--- mm/memremap.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
mm/memremap.c +2 -1
@@ -302,7 +302,8 @@ static int pagemap_range(struct dev_pagemap *pgmap, struct mhp_params *params,return 0 ; err_add_memory: -kasan_remove_zero_shadow (__va (range->start),range_len (range)); +if (!is_private) +kasan_remove_zero_shadow (__va (range->start),range_len (range)); err_kasan:untrack_pfn (NULL ,PHYS_PFN (range->start),range_len (range)); err_pfn_remap:
Signature · 1 line
2.23.0
Quoted 6 lines · Miaohe Lin
For device private memory, we do not create a linear mapping for the memory because the device memory is un-accessible. Thus we do not add kasan zero shadow for it. So it's unnecessary to do
kasan_remove_zero_shadow()for it.Signed-off-by Miaohe Lin <[email protected]>
Good catch.
Reviewed-by Muchun Song <[email protected]>