mm-memremap-avoid-calling-kasan_remove_zero_shadow-for-device-private-memory.patch removed from -mm tree
The patch titled
Subject: mm/memremap: avoid calling kasan_remove_zero_shadow() for device private memory
has been removed from the -mm tree. Its filename was
mm-memremap-avoid-calling-kasan_remove_zero_shadow-for-device-private-memory.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
From: Miaohe Lin <[email protected]>
Subject: 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.
---
mm/memremap.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
mm/memremap.c renamed from mm/memremap.c~mm-memremap-avoid-calling-kasan_remove_zero_shadow-for-device-private-memory +2 -1
@@ -282,7 +282,8 @@ static int pagemap_range(struct dev_pagereturn 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:
_
Patches currently in -mm which might be from [email protected] are
mm-huge_memory-make-is_transparent_hugepage-static.patch