The patch titled
Subject: mm-hugetlb-take-refcount-under-page-table-lock-in-follow_huge_pmd-fix
has been removed from the -mm tree. Its filename was
mm-hugetlb-take-refcount-under-page-table-lock-in-follow_huge_pmd-fix.patch
This patch was dropped because it was folded into mm-hugetlb-take-refcount-under-page-table-lock-in-follow_huge_pmd.patch
------------------------------------------------------
From: Naoya Horiguchi <n-horiguchi@xxxxxxxxxxxxx>
Subject: mm-hugetlb-take-refcount-under-page-table-lock-in-follow_huge_pmd-fix
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
mm/hugetlb.c | 8 ++++++++
1 file changed, 8 insertions(+)
diff -puN mm/hugetlb.c~mm-hugetlb-take-refcount-under-page-table-lock-in-follow_huge_pmd-fix mm/hugetlb.c
--- a/mm/hugetlb.c~mm-hugetlb-take-refcount-under-page-table-lock-in-follow_huge_pmd-fix
+++ a/mm/hugetlb.c
@@ -3690,6 +3690,14 @@ follow_huge_pud(struct mm_struct *mm, un
#endif /* CONFIG_ARCH_WANT_GENERAL_HUGETLB */
+/*
+ * This function calls the architecture dependent variant follow_huge_pmd()
+ * with holding page table lock depending on FOLL_GET.
+ * Whether hugepage migration is supported or not, follow() can be called
+ * with FOLL_GET from do_move_page_to_node_array(), so we need do this in
+ * common code.
+ * Should be called under read mmap_sem.
+ */
struct page *follow_huge_pmd_lock(struct vm_area_struct *vma,
unsigned long address, pmd_t *pmd, int flags)
{
_
Patches currently in -mm which might be from n-horiguchi@xxxxxxxxxxxxx are
origin.patch
memory-hotplug-add-sysfs-zones_online_to-attribute.patch
mm-hugetlb-take-refcount-under-page-table-lock-in-follow_huge_pmd.patch
mm-hugetlb-use-get_page_unless_zero-in-hugetlb_fault.patch
mm-hugetlb-add-migration-entry-check-in-hugetlb_change_protection.patch
mm-hugetlb-remove-unused-argument-of-follow_huge_pmdpud.patch
mm-introduce-do_shared_fault-and-drop-do_fault-fix-fix.patch
do_shared_fault-check-that-mmap_sem-is-held.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
