From: syzbot ci <syzbot+ci49b1eaed80c7d30c@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: mm, hugetlb: implement movable_gigantic_pages sysctl
Date: Thu, 18 Dec 2025 08:22:45 -0800 [thread overview]
Message-ID: <69442a55.a70a0220.207337.00e6.GAE@google.com> (raw)
syzbot ci has tested the following series
[v4] mm, hugetlb: implement movable_gigantic_pages sysctl
https://lore.kernel.org/all/20251218151211.1237411-1-gourry@gourry.net
* [PATCH v4] mm, hugetlb: implement movable_gigantic_pages sysctl
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/d52fdf02-5dcf-4301-a1cf-3f4ef9cfc4fc
***
kernel build error
tree: mm-new
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/akpm/mm.git
base: c642ecda5b136882e518d8303863473c0d21ab2f
arch: amd64
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
config: https://ci.syzbot.org/builds/2bd0cdd1-8fa9-4367-a9fc-9255e4e05b96/config
mm/hugetlb.c:505:9: error: incomplete definition of type 'struct hugetlb_cgroup'
mm/hugetlb.c:506:19: error: incomplete definition of type 'struct hugetlb_cgroup'
mm/hugetlb.c:517:16: error: incomplete definition of type 'struct hugetlb_cgroup'
mm/hugetlb.c:587:39: error: incompatible pointer types passing 'struct hugetlb_cgroup *' to parameter of type 'struct hugetlb_cgroup *' [-Werror,-Wincompatible-pointer-types]
mm/hugetlb.c:646:26: error: incompatible pointer types passing 'struct hugetlb_cgroup *' to parameter of type 'struct hugetlb_cgroup *' [-Werror,-Wincompatible-pointer-types]
mm/hugetlb.c:659:16: error: incompatible pointer types passing 'struct hugetlb_cgroup *' to parameter of type 'struct hugetlb_cgroup *' [-Werror,-Wincompatible-pointer-types]
mm/hugetlb.c:776:45: error: incompatible pointer types passing 'struct hugetlb_cgroup *' to parameter of type 'struct hugetlb_cgroup *' [-Werror,-Wincompatible-pointer-types]
mm/hugetlb.c:909:4: error: call to undeclared function 'hugetlb_cgroup_uncharge_file_region'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
mm/hugetlb.c:930:4: error: call to undeclared function 'hugetlb_cgroup_uncharge_file_region'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
mm/hugetlb.c:938:4: error: call to undeclared function 'hugetlb_cgroup_uncharge_file_region'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
mm/hugetlb.c:944:4: error: call to undeclared function 'hugetlb_cgroup_uncharge_file_region'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
mm/hugetlb.c:1107:9: error: incomplete definition of type 'struct hugetlb_cgroup'
mm/hugetlb.c:1109:24: error: incomplete definition of type 'struct hugetlb_cgroup'
mm/hugetlb.c:1287:3: error: call to undeclared function 'resv_map_put_hugetlb_cgroup_uncharge_info'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
mm/hugetlb.c:1479:18: error: call to undeclared function 'hugetlb_cgroup_from_folio'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
mm/hugetlb.c:1480:18: error: call to undeclared function 'hugetlb_cgroup_from_folio_rsvd'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
mm/hugetlb.c:1483:6: error: call to undeclared function 'hstate_is_gigantic_no_runtime'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
mm/hugetlb.c:1545:6: error: call to undeclared function 'hstate_is_gigantic_no_runtime'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
mm/hugetlb.c:1807:2: error: call to undeclared function 'hugetlb_cgroup_uncharge_folio'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
***
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.
The email will later be sent to:
[akpm@linux-foundation.org brauner@kernel.org corbet@lwn.net david@kernel.org david@redhat.com gourry@gourry.net hannes@cmpxchg.org jack@suse.cz joel.granados@kernel.org kernel-team@meta.com laoar.shao@gmail.com liam.howlett@oracle.com linux-doc@vger.kernel.org linux-kernel@vger.kernel.org linux-mm@kvack.org lorenzo.stoakes@oracle.com mclapinski@google.com mgorman@suse.de mhocko@suse.com muchun.song@linux.dev osalvador@suse.de rientjes@google.com rppt@kernel.org surenb@google.com vbabka@suse.cz]
If the report looks fine to you, reply with:
#syz upstream
next reply other threads:[~2025-12-18 16:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-18 16:22 syzbot ci [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-12-03 7:34 [moderation/CI] Re: mm, hugetlb: implement movable_gigantic_pages sysctl syzbot ci
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=69442a55.a70a0220.207337.00e6.GAE@google.com \
--to=syzbot+ci49b1eaed80c7d30c@syzkaller.appspotmail.com \
--cc=syzbot@lists.linux.dev \
--cc=syzkaller-upstream-moderation@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox