[moderation/CI] Re: mm/hugetlb: fix resv_map memory leak in __mmap_region error path

[syzbot ci <syzbot+cifd696a6f8ad82c74@syzkaller.appspotmail.com>]

syzbot ci has tested the following series

[v1] mm/hugetlb: fix resv_map memory leak in __mmap_region error path
https://lore.kernel.org/all/20260425070700.562229-1-25181214217@stu.xidian.edu.cn
* [RFC PATCH] mm/hugetlb: fix resv_map memory leak in __mmap_region error path

and found the following issue:
kernel build error

Full report is available here:
https://ci.syzbot.org/series/266de6ea-d980-4f3a-a2fc-436d995c94df

***

kernel build error

tree:      mm-new
URL:       https://kernel.googlesource.com/pub/scm/linux/kernel/git/akpm/mm.git
base:      f47fc45d9080d6a06fe1001a5e9798bb4c9c2361
arch:      amd64
compiler:  Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
config:    https://ci.syzbot.org/builds/4a6ae9e2-abb3-4759-ae76-1f73f316196f/config

mm/vma.c:2804:26: error: incompatible pointer types passing 'struct vm_area_desc *' to parameter of type 'struct vm_area_desc *' [-Werror,-Wincompatible-pointer-types]
fs/hugetlbfs/inode.c:183:27: error: incompatible function pointer types assigning to 'void (*)(struct vm_area_desc *)' from 'void (struct vm_area_desc *)' [-Wincompatible-function-pointer-types]

***

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 patch for this bug, please reply with `#syz test`
(should be on a separate line).

The patch should be attached to the email.
Note: arguments like custom git repos and branches are not supported.

The email will later be sent to:
[25181214217@stu.xidian.edu.cn akpm@linux-foundation.org liam.howlett@oracle.com linux-kernel@vger.kernel.org linux-mm@kvack.org muchun.song@linux.dev]

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

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