From: syzbot ci <syzbot+ci8566aa695dc7efec@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: tweaks for costly order __GFP_NORETRY reclaim
Date: Tue, 16 Dec 2025 10:05:58 -0800 [thread overview]
Message-ID: <69419f86.a70a0220.25eec0.0004.GAE@google.com> (raw)
syzbot ci has tested the following series
[v1] tweaks for costly order __GFP_NORETRY reclaim
https://lore.kernel.org/all/20251216-thp-thisnode-tweak-v1-0-0e499d13d2eb@suse.cz
* [PATCH RFC 1/2] mm, page_alloc, thp: prevent reclaim for __GFP_THISNODE THP allocations
* [PATCH RFC 2/2] mm, page_alloc: fail costly __GFP_NORETRY allocations faster
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/d26c9b4f-cf40-46e9-a5a8-388488c71904
***
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/6cf2accb-ad00-42a0-a354-545bfd39b6cb/config
mm/page_alloc.c:4936:1: error: function definition is not allowed here
mm/page_alloc.c:5004:1: error: function definition is not allowed here
mm/page_alloc.c:5152:1: error: function definition is not allowed here
mm/page_alloc.c:5217:1: error: function definition is not allowed here
mm/page_alloc.c:5229:1: error: function definition is not allowed here
mm/page_alloc.c:5242:1: error: function definition is not allowed here
mm/page_alloc.c:5253:1: error: function definition is not allowed here
mm/page_alloc.c:5260:1: error: function definition is not allowed here
mm/page_alloc.c:5304:1: error: function definition is not allowed here
mm/page_alloc.c:5314:1: error: function definition is not allowed here
mm/page_alloc.c:5328:1: error: function definition is not allowed here
mm/page_alloc.c:5339:1: error: function definition is not allowed here
mm/page_alloc.c:5374:1: error: function definition is not allowed here
mm/page_alloc.c:5399:1: error: function definition is not allowed here
mm/page_alloc.c:5420:1: error: function definition is not allowed here
mm/page_alloc.c:5444:1: error: function definition is not allowed here
mm/page_alloc.c:5473:1: error: function definition is not allowed here
mm/page_alloc.c:5479:1: error: function definition is not allowed here
mm/page_alloc.c:5490:1: error: function definition is not allowed here
***
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 david@kernel.org hannes@cmpxchg.org jackmanb@google.com joshua.hahnjy@gmail.com liam.howlett@oracle.com linux-kernel@vger.kernel.org linux-mm@kvack.org lorenzo.stoakes@oracle.com mhocko@suse.com pfalcato@suse.de rientjes@google.com rppt@kernel.org surenb@google.com vbabka@suse.cz ziy@nvidia.com]
If the report looks fine to you, reply with:
#syz upstream
reply other threads:[~2025-12-16 18:05 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=69419f86.a70a0220.25eec0.0004.GAE@google.com \
--to=syzbot+ci8566aa695dc7efec@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