From: syzbot ci <syzbot+ci224332cbd3a28fc6@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: mm/huge_memory: refactor zap_huge_pmd()
Date: Sat, 21 Mar 2026 12:58:53 -0700 [thread overview]
Message-ID: <69bef87d.050a0220.3bf4de.005e.GAE@google.com> (raw)
syzbot ci has tested the following series
[v3] mm/huge_memory: refactor zap_huge_pmd()
https://lore.kernel.org/all/cover.1774029655.git.ljs@kernel.org
* [PATCH v3 01/13] mm/huge_memory: simplify vma_is_specal_huge()
* [PATCH v3 02/13] mm/huge: avoid big else branch in zap_huge_pmd()
* [PATCH v3 03/13] mm/huge_memory: have zap_huge_pmd return a boolean, add kdoc
* [PATCH v3 04/13] mm/huge_memory: handle buggy PMD entry in zap_huge_pmd()
* [PATCH v3 05/13] mm/huge_memory: add a common exit path to zap_huge_pmd()
* [PATCH v3 06/13] mm/huge_memory: remove unnecessary VM_BUG_ON_PAGE()
* [PATCH v3 07/13] mm/huge_memory: deduplicate zap deposited table call
* [PATCH v3 08/13] mm/huge_memory: remove unnecessary sanity checks
* [PATCH v3 09/13] mm/huge_memory: use mm instead of tlb->mm
* [PATCH v3 10/13] mm/huge_memory: separate out the folio part of zap_huge_pmd()
* [PATCH v3 11/13] mm: add softleaf_is_valid_pmd_entry(), pmd_to_softleaf_folio()
* [PATCH v3 12/13] mm/huge_memory: add and use normal_or_softleaf_folio_pmd()
* [PATCH v3 13/13] mm/huge_memory: add and use has_deposited_pgtable()
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/c3a7df63-9a98-4280-89d6-8095fc66d91b
***
kernel build error
tree: torvalds
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux
base: a0c83177734ab98623795e1ba2cf4b72c23de5e7
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/e9989b7c-5e25-414f-babe-85b146b1c0ba/config
mm/huge_memory.c:108:9: error: call to undeclared function 'vma_test_any'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
mm/huge_memory.c:4615:6: error: call to undeclared function 'vma_test'; 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 baohua@kernel.org baolin.wang@linux.alibaba.com david@kernel.org dev.jain@arm.com kas@kernel.org lance.yang@linux.dev liam.howlett@oracle.com linux-kernel@vger.kernel.org linux-mm@kvack.org ljs@kernel.org mhocko@suse.com npache@redhat.com rppt@kernel.org ryan.roberts@arm.com surenb@google.com vbabka@kernel.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
next reply other threads:[~2026-03-21 19:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-21 19:58 syzbot ci [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-03-20 13:20 [moderation/CI] Re: mm/huge_memory: refactor zap_huge_pmd() 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=69bef87d.050a0220.3bf4de.005e.GAE@google.com \
--to=syzbot+ci224332cbd3a28fc6@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