The patch titled Subject: hugetlb-pass-vma-into-huge_pte_alloc-and-huge_pmd_share-fix has been added to the -mm tree. Its filename is hugetlb-pass-vma-into-huge_pte_alloc-and-huge_pmd_share-fix.patch This patch should soon appear at https://ozlabs.org/~akpm/mmots/broken-out/hugetlb-pass-vma-into-huge_pte_alloc-and-huge_pmd_share-fix.patch and later at https://ozlabs.org/~akpm/mmotm/broken-out/hugetlb-pass-vma-into-huge_pte_alloc-and-huge_pmd_share-fix.patch Before you just go and hit "reply", please: a) Consider who else should be cc'ed b) Prefer to cc a suitable mailing list as well c) Ideally: find the original patch on the mailing list and do a reply-to-all to that, adding suitable additional cc's *** Remember to use Documentation/process/submit-checklist.rst when testing your code *** The -mm tree is included into linux-next and is updated there every 3-4 working days ------------------------------------------------------ From: Peter Xu <peterx@xxxxxxxxxx> Subject: hugetlb-pass-vma-into-huge_pte_alloc-and-huge_pmd_share-fix build fix Link: https://lkml.kernel.org/r/20210304164653.GB397383@xz-x1 Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- mm/hugetlb.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --- a/mm/hugetlb.c~hugetlb-pass-vma-into-huge_pte_alloc-and-huge_pmd_share-fix +++ a/mm/hugetlb.c @@ -5392,7 +5392,7 @@ int huge_pmd_unshare(struct mm_struct *m } #define want_pmd_share() (1) #else /* !CONFIG_ARCH_WANT_HUGE_PMD_SHARE */ -pte_t *huge_pmd_share(struct mm_struct *mm, struct vm_area_struct vma, +pte_t *huge_pmd_share(struct mm_struct *mm, struct vm_area_struct *vma, unsigned long addr, pud_t *pud) { return NULL; _ Patches currently in -mm which might be from peterx@xxxxxxxxxx are hugetlb-pass-vma-into-huge_pte_alloc-and-huge_pmd_share.patch hugetlb-pass-vma-into-huge_pte_alloc-and-huge_pmd_share-fix.patch hugetlb-userfaultfd-forbid-huge-pmd-sharing-when-uffd-enabled.patch mm-hugetlb-move-flush_hugetlb_tlb_range-into-hugetlbh.patch hugetlb-userfaultfd-unshare-all-pmds-for-hugetlbfs-when-register-wp.patch