[akpm-mm:mm-new 302/317] mm/memory.c:2271:17: error: too many arguments to function 'hugetlb_zap_begin'; expected 3, have 4

[kernel test robot <lkp@intel.com>]

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-new
head:   2aeb49124a2b3d0c9aa8c0a2124c8cae21ab4e0b
commit: f1fc44daf6183604b96243805877ee0b1626daaf [302/317] mm/hugetlb: don't lock private resv_map during final unmap
config: openrisc-allnoconfig (https://download.01.org/0day-ci/archive/20260904/202609041213.bgAPQEek-lkp@intel.com/config)
compiler: or1k-linux-gcc (GCC) 16.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260904/202609041213.bgAPQEek-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202609041213.bgAPQEek-lkp@intel.com/

All errors (new ones prefixed by >>):

   mm/memory.c: In function 'unmap_vmas':
>> mm/memory.c:2271:17: error: too many arguments to function 'hugetlb_zap_begin'; expected 3, have 4
    2271 |                 hugetlb_zap_begin(vma, &start, &end, &details);
         |                 ^~~~~~~~~~~~~~~~~                    ~~~~~~~~
   In file included from mm/memory.c:48:
   include/linux/hugetlb.h:322:20: note: declared here
     322 | static inline void hugetlb_zap_begin(
         |                    ^~~~~~~~~~~~~~~~~


vim +/hugetlb_zap_begin +2271 mm/memory.c

  2238	
  2239	/**
  2240	 * unmap_vmas - unmap a range of memory covered by a list of vma's
  2241	 * @tlb: address of the caller's struct mmu_gather
  2242	 * @unmap: The unmap_desc
  2243	 *
  2244	 * Unmap all pages in the vma list.
  2245	 *
  2246	 * Only addresses between `start' and `end' will be unmapped.
  2247	 *
  2248	 * The VMA list must be sorted in ascending virtual address order.
  2249	 *
  2250	 * unmap_vmas() assumes that the caller will flush the whole unmapped address
  2251	 * range after unmap_vmas() returns.  So the only responsibility here is to
  2252	 * ensure that any thus-far unmapped pages are flushed before unmap_vmas()
  2253	 * drops the lock and schedules.
  2254	 */
  2255	void unmap_vmas(struct mmu_gather *tlb, struct unmap_desc *unmap)
  2256	{
  2257		struct vm_area_struct *vma;
  2258		struct mmu_notifier_range range;
  2259		struct zap_details details = {
  2260			.zap_flags = ZAP_FLAG_DROP_MARKER | ZAP_FLAG_UNMAP,
  2261		};
  2262	
  2263		vma = unmap->first;
  2264		mmu_notifier_range_init(&range, MMU_NOTIFY_UNMAP, 0, vma->vm_mm,
  2265					unmap->vma_start, unmap->vma_end);
  2266		mmu_notifier_invalidate_range_start(&range);
  2267		do {
  2268			unsigned long start = max(vma->vm_start, unmap->vma_start);
  2269			unsigned long end = min(vma->vm_end, unmap->vma_end);
  2270	
> 2271			hugetlb_zap_begin(vma, &start, &end, &details);
  2272			__zap_vma_range(tlb, vma, start, end, &details);
  2273			hugetlb_zap_end(vma, &details);
  2274			vma = mas_find(unmap->mas, unmap->tree_end - 1);
  2275		} while (vma);
  2276		mmu_notifier_invalidate_range_end(&range);
  2277	}
  2278	

--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki