All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot ci <syzbot+cie486b10a0a53fc6c@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: Fri, 20 Mar 2026 06:20:31 -0700	[thread overview]
Message-ID: <69bd499f.050a0220.3bf4de.0023.GAE@google.com> (raw)

syzbot ci has tested the following series

[v2] mm/huge_memory: refactor zap_huge_pmd()
https://lore.kernel.org/all/cover.1773924928.git.ljs@kernel.org
* [PATCH v2 1/9] mm/huge_memory: simplify vma_is_specal_huge()
* [PATCH v2 2/9] mm/huge: avoid big else branch in zap_huge_pmd()
* [PATCH v2 3/9] mm/huge_memory: have zap_huge_pmd return a boolean, add kdoc
* [PATCH v2 4/9] mm/huge_memory: handle buggy PMD entry in zap_huge_pmd()
* [PATCH v2 5/9] mm/huge_memory: add a common exit path to zap_huge_pmd()
* [PATCH v2 6/9] mm/huge_memory: remove unnecessary VM_BUG_ON_PAGE()
* [PATCH v2 7/9] mm/huge_memory: deduplicate zap deposited table call
* [PATCH v2 8/9] mm/huge_memory: deduplicate zap_huge_pmd() further by tracking state
* [PATCH v2 9/9] mm/huge_memory: have zap_huge_pmd() use vm_normal_folio_pmd()

and found the following issue:
kernel build error

Full report is available here:
https://ci.syzbot.org/series/fc789267-30ea-4c5c-8e1f-623cee399460

***

kernel build error

tree:      mm-new
URL:       https://kernel.googlesource.com/pub/scm/linux/kernel/git/akpm/mm.git
base:      aa0a550d268b3075b67568d915b7093aabbb0772
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/b61f81fb-cab5-4257-8eaf-4693791b0a7a/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:4596: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 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


             reply	other threads:[~2026-03-20 13:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-20 13:20 syzbot ci [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-03-21 19:58 [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=69bd499f.050a0220.3bf4de.0023.GAE@google.com \
    --to=syzbot+cie486b10a0a53fc6c@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.