From: syzbot ci <syzbot+ci709c6b85505bf415@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: mm: khugepaged: make scan loops suspend aware
Date: Tue, 10 Feb 2026 19:55:16 -0800 [thread overview]
Message-ID: <698bfda4.050a0220.2eeac1.0093.GAE@google.com> (raw)
syzbot ci has tested the following series
[v1] mm: khugepaged: make scan loops suspend aware
https://lore.kernel.org/all/20260211030024.232964-1-senozhatsky@chromium.org
* [PATCH] mm: khugepaged: make scan loops suspend aware
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/2ff9a9e1-d2c9-404f-abdc-6e4e11db1ec0
***
kernel build error
tree: mm-new
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/akpm/mm.git
base: 92dbb8c3997c9148eb37095eb0c2a4d02489ad12
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/60005f39-0e81-4ff1-a9f9-2981b6ac9520/config
mm/khugepaged.c:915:53: error: too few arguments to function call, expected 2, have 1
mm/khugepaged.c:2440:53: error: too few arguments to function call, expected 2, have 1
mm/khugepaged.c:2448:54: error: too few arguments to function call, expected 2, have 1
mm/khugepaged.c:2470:55: error: too few arguments to function call, expected 2, have 1
mm/khugepaged.c:2488:48: error: too few arguments to function call, expected 2, have 1
***
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 baohua@kernel.org baolin.wang@linux.alibaba.com david@kernel.org dev.jain@arm.com lance.yang@linux.dev liam.howlett@oracle.com linux-kernel@vger.kernel.org linux-mm@kvack.org lorenzo.stoakes@oracle.com npache@redhat.com ryan.roberts@arm.com senozhatsky@chromium.org ziy@nvidia.com]
If the report looks fine to you, reply with:
#syz upstream
If the report is a false positive, reply with
#syz invalid
reply other threads:[~2026-02-11 3:55 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=698bfda4.050a0220.2eeac1.0093.GAE@google.com \
--to=syzbot+ci709c6b85505bf415@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