From: syzbot ci <syzbot+ci74bc0c65f3724fb4@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: mm/memory: fix hugetlb_zap_begin() call in zap_vma_range_batched()
Date: Sat, 05 Sep 2026 02:05:06 -0700 [thread overview]
Message-ID: <6a9bdb42.a5e650b3.26d8a.0009.GAE@google.com> (raw)
syzbot ci has tested the following series
[v1] mm/memory: fix hugetlb_zap_begin() call in zap_vma_range_batched()
https://lore.kernel.org/all/20260904000028.149656-1-sj@kernel.org
* [PATCH] mm/memory: fix hugetlb_zap_begin() call in zap_vma_range_batched()
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/62239cdd-0901-45e4-ba20-e2ae8e212ee8
***
kernel build error
tree: mm-new
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/akpm/mm.git
base: e3fc12b08aadde9cec7b3799ac0e0c9a1aa245c4
arch: amd64
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
config: https://ci.syzbot.org/builds/44bbebee-2095-4bcb-be13-5072c427460b/config
mm/memory.c:2307:51: error: too many arguments to function call, expected 3, have 4
***
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 fix for this bug, please reply with `#syz test`
(on a separate line) and attach the patch to the email.
Notes:
- The patch will be applied on top of the tested series (as an
incremental fix).
- To test a new version of the whole series, please send it directly
to syzbot@lists.linux.dev.
- Arguments like custom git repos and branches are not supported.
The email will later be sent to:
[akpm@linux-foundation.org david@kernel.org liam@infradead.org linux-kernel@vger.kernel.org linux-mm@kvack.org ljs@kernel.org mhocko@suse.com rppt@kernel.org sj@kernel.org surenb@google.com vbabka@kernel.org]
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-09-05 9: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=6a9bdb42.a5e650b3.26d8a.0009.GAE@google.com \
--to=syzbot+ci74bc0c65f3724fb4@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