Archive-only list for syzbot
 help / color / mirror / Atom feed
From: syzbot ci <syzbot+cid561235c8b6f0f02@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: mm, bpf: BPF-MM, BPF-THP
Date: Wed, 15 Oct 2025 09:17:40 -0700	[thread overview]
Message-ID: <68efc924.050a0220.91a22.02a2.GAE@google.com> (raw)

syzbot ci has tested the following series

[v10] mm, bpf: BPF-MM, BPF-THP
https://lore.kernel.org/all/20251015141716.887-1-laoar.shao@gmail.com
* [RFC PATCH v10 mm-new 1/9] mm: thp: remove vm_flags parameter from khugepaged_enter_vma()
* [RFC PATCH v10 mm-new 2/9] mm: thp: remove vm_flags parameter from thp_vma_allowable_order()
* [RFC PATCH v10 mm-new 3/9] mm: thp: add support for BPF based THP order selection
* [RFC PATCH v10 mm-new 4/9] mm: thp: decouple THP allocation between swap and page fault paths
* [RFC PATCH v10 mm-new 5/9] mm: thp: enable THP allocation exclusively through khugepaged
* [RFC PATCH v10 mm-new 6/9] bpf: mark mm->owner as __safe_rcu_or_null
* [RFC PATCH v10 mm-new 7/9] bpf: mark vma->vm_mm as __safe_trusted_or_null
* [RFC PATCH v10 mm-new 8/9] selftests/bpf: add a simple BPF based THP policy
* [RFC PATCH v10 mm-new 9/9] Documentation: add BPF-based THP policy management

and found the following issue:
kernel build error

Full report is available here:
https://ci.syzbot.org/series/a8a425e8-ff46-4bac-bf93-1ee0aad0c36a

***

kernel build error

tree:      bpf-next
URL:       https://kernel.googlesource.com/pub/scm/linux/kernel/git/bpf/bpf-next.git
base:      56b4d162392dda2365fbc1f482184a24b489d07d
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/7b9d324c-f37b-4dfb-bbb3-f6ff6b11b136/config

kernel/fork.c:1133:2: error: call to undeclared function 'bpf_thp_exit_mm'; 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:
[21cnbao@gmail.com akpm@linux-foundation.org ameryhung@gmail.com andrii@kernel.org ast@kernel.org baolin.wang@linux.alibaba.com bpf@vger.kernel.org corbet@lwn.net daniel@iogearbox.net david@redhat.com dev.jain@arm.com gutierrez.asier@huawei-partners.com hannes@cmpxchg.org lance.yang@linux.dev laoar.shao@gmail.com liam.howlett@oracle.com linux-doc@vger.kernel.org linux-kernel@vger.kernel.org linux-mm@kvack.org lorenzo.stoakes@oracle.com npache@redhat.com rdunlap@infradead.org rientjes@google.com ryan.roberts@arm.com shakeel.butt@linux.dev shy828301@gmail.com tj@kernel.org usamaarif642@gmail.com willy@infradead.org ziy@nvidia.com]

If the report looks fine to you, reply with:
#syz upstream


                 reply	other threads:[~2025-10-15 16:17 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=68efc924.050a0220.91a22.02a2.GAE@google.com \
    --to=syzbot+cid561235c8b6f0f02@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