Commit f1fc44daf618 ("mm/hugetlb: don't lock private resv_map during final unmap") added zap_details parameter to hugetlb_zap_begin(). But the hugetlb_zap_begin() call in zap_vma_range_batched() is not updated. As a result, build fails as below. Fix it. CC mm/memory.o .../mm/memory.c: In function ‘zap_vma_range_batched’: .../mm/memory.c:2308:9: error: too few arguments to function ‘hugetlb_zap_begin’ 2308 | hugetlb_zap_begin(vma, &range.start, &range.end); | ^~~~~~~~~~~~~~~~~ In file included from .../mm/memory.c:48: .../include/linux/hugetlb.h:253:20: note: declared here 253 | static inline void hugetlb_zap_begin(struct vm_area_struct *vma, | ^~~~~~~~~~~~~~~~~ /* TODO: move below to commentary */ I didn't read the broken commit in depth. This fix is only build-tested. I wanted to report the issue with this as a temporal fix, but the broken commit doesn't have Link: tag. So directly posting this temporal and not very well verified fix first. Fixes: Fixes: f1fc44daf618 ("mm/hugetlb: don't lock private resv_map during final unmap") Signed-off-by: SJ Park --- mm/memory.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/mm/memory.c b/mm/memory.c index fcf893f4b55e2..151a1bf512e00 100644 --- a/mm/memory.c +++ b/mm/memory.c @@ -2305,7 +2305,7 @@ void zap_vma_range_batched(struct mmu_gather *tlb, mmu_notifier_range_init(&range, MMU_NOTIFY_CLEAR, 0, vma->vm_mm, address, end); - hugetlb_zap_begin(vma, &range.start, &range.end); + hugetlb_zap_begin(vma, &range.start, &range.end, details); update_hiwater_rss(vma->vm_mm); mmu_notifier_invalidate_range_start(&range); /* base-commit: 2d1388907095f676b59fe6dd22f244abc08408cf -- 2.47.3