From: syzbot ci <syzbot+ci9c2f2c7f0dfb6460@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: page_alloc: allow migration of smaller hugepages during contig_alloc
Date: Tue, 02 Dec 2025 23:16:08 -0800 [thread overview]
Message-ID: <692fe3b8.a70a0220.2ea503.00cc.GAE@google.com> (raw)
syzbot ci has tested the following series
[v4] page_alloc: allow migration of smaller hugepages during contig_alloc
https://lore.kernel.org/all/20251203063004.185182-1-gourry@gourry.net
* [PATCH v4] page_alloc: allow migration of smaller hugepages during contig_alloc
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/38366b6e-ec98-470f-8c10-780a2228255f
***
kernel build error
tree: kvm-next
URL: https://kernel.googlesource.com/pub/scm/virt/kvm/kvm/
base: 6b36119b94d0b2bb8cea9d512017efafd461d6ac
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/bc635f01-9ae9-4058-b199-3375952e2af9/config
mm/page_alloc.c:7013:18: error: use of undeclared identifier 'MAX_FOLIO_ORDER'
***
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 dave.hansen@linux.intel.com david@redhat.com gourry@gourry.net hannes@cmpxchg.org jackmanb@google.com joshua.hahnjy@gmail.com kas@kernel.org kernel-team@meta.com kvm@vger.kernel.org linux-coco@lists.linux.dev linux-kernel@vger.kernel.org linux-mm@kvack.org mhocko@suse.com muchun.song@linux.dev osalvador@suse.de richard.weiyang@gmail.com rick.p.edgecombe@intel.com rientjes@google.com surenb@google.com vbabka@suse.cz x86@kernel.org ziy@nvidia.com]
If the report looks fine to you, reply with:
#syz upstream
reply other threads:[~2025-12-03 7:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=692fe3b8.a70a0220.2ea503.00cc.GAE@google.com \
--to=syzbot+ci9c2f2c7f0dfb6460@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.