mm-hmm-fix-bad-subpage-pointer-in-try_to_unmap_one.patch removed from -mm tree
The patch titled
Subject: mm/hmm: fix bad subpage pointer in try_to_unmap_one
has been removed from the -mm tree. Its filename was
mm-hmm-fix-bad-subpage-pointer-in-try_to_unmap_one.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
From: Ralph Campbell <[email protected]>
Subject: mm/hmm: fix bad subpage pointer in try_to_unmap_one
When migrating an anonymous private page to a ZONE_DEVICE private page, the source page->mapping and page->index fields are copied to the destination ZONE_DEVICE struct page and the page_mapcount() is increased. This is so rmap_walk() can be used to unmap and migrate the page back to system memory. However, try_to_unmap_one() computes the subpage pointer from a swap pte which computes an invalid page pointer and a kernel panic results such as:
BUG: unable to handle page fault for address: ffffea1fffffffc8
Currently, only single pages can be migrated to device private memory so no subpage computation is needed and it can be set to "page".
---
mm/rmap.c | 8 ++++++++ 1 file changed, 8 insertions(+)
mm/rmap.c renamed from mm/rmap.c~mm-hmm-fix-bad-subpage-pointer-in-try_to_unmap_one +8 -0
@@ -1475,7 +1475,15 @@ static bool try_to_unmap_one(struct page/* * No need to invalidate here it will synchronize on * against the special swap migration pte. +* +* The assignment to subpage above was computed from a +* swap PTE which results in an invalid pointer. +* Since only PAGE_SIZE pages can currently be +* migrated, just set it to page. This will need to be +* changed when hugepage migrations to device private +* memory are supported. */ + subpage = page; goto discard; }
_
Patches currently in -mm which might be from [email protected] are