[moderation/CI] Re: mm/memory: fix hugetlb_zap_begin() call in zap_vma_range_batched()

[moderation/CI] Re: mm/memory: fix hugetlb_zap_begin() call in zap_vma_range_batched()

[syzbot ci]

syzbot ci has tested the following series

[v1] mm/memory: fix hugetlb_zap_begin() call in zap_vma_range_batched()
https://lore.kernel.org/all/20260904000028.149656-1-sj@kernel.org
* [PATCH] mm/memory: fix hugetlb_zap_begin() call in zap_vma_range_batched()

and found the following issue:
kernel build error

Full report is available here:
https://ci.syzbot.org/series/62239cdd-0901-45e4-ba20-e2ae8e212ee8

***

kernel build error

tree:      mm-new
URL:       https://kernel.googlesource.com/pub/scm/linux/kernel/git/akpm/mm.git
base:      e3fc12b08aadde9cec7b3799ac0e0c9a1aa245c4
arch:      amd64
compiler:  Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
config:    https://ci.syzbot.org/builds/44bbebee-2095-4bcb-be13-5072c427460b/config

mm/memory.c:2307:51: error: too many arguments to function call, expected 3, have 4

***

If these findings have caused you to resend the series or submit a
separate fix, please add the following tag to your commit message:
  Tested-by: syzbot@syzkaller.appspotmail.com

---
This report is generated by a bot. It may contain errors.
syzbot ci engineers can be reached at syzkaller@googlegroups.com.

To test a fix for this bug, please reply with `#syz test`
(on a separate line) and attach the patch to the email.

Notes:
- The patch will be applied on top of the tested series (as an
  incremental fix).
- To test a new version of the whole series, please send it directly
  to syzbot@lists.linux.dev.
- Arguments like custom git repos and branches are not supported.

The email will later be sent to:
[akpm@linux-foundation.org david@kernel.org liam@infradead.org linux-kernel@vger.kernel.org linux-mm@kvack.org ljs@kernel.org mhocko@suse.com rppt@kernel.org sj@kernel.org surenb@google.com vbabka@kernel.org]

If the report looks fine to you, reply with:
#syz upstream

If the report is a false positive, reply with
#syz invalid