From: syzbot ci <syzbot+cia45a30af98595083@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: A subsystem for hot page detection and promotion
Date: Fri, 15 Aug 2025 09:28:58 -0700 [thread overview]
Message-ID: <689f604a.050a0220.e29e5.001d.GAE@google.com> (raw)
syzbot ci has tested the following series
[v1] A subsystem for hot page detection and promotion
https://lore.kernel.org/all/20250814134826.154003-1-bharata@amd.com
* [RFC PATCH v1 1/7] mm: migrate: Allow misplaced migration without VMA too
* [RFC PATCH v1 2/7] migrate: implement migrate_misplaced_folios_batch
* [RFC PATCH v1 3/7] mm: Hot page tracking and promotion
* [RFC PATCH v1 4/7] x86: ibs: In-kernel IBS driver for memory access profiling
* [RFC PATCH v1 5/7] x86: ibs: Enable IBS profiling for memory accesses
* [RFC PATCH v1 6/7] mm: mglru: generalize page table walk
* [RFC PATCH v1 7/7] mm: klruscand: use mglru scanning for page promotion
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/28a4d048-e6a3-4f88-9af0-a125dc83ce59
***
kernel build error
tree: torvalds
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux
base: dfc0f6373094dd88e1eaf76c44f2ff01b65db851
arch: amd64
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
config: https://ci.syzbot.org/builds/e83820a3-9192-43d7-875e-200f41909c3c/config
make[3]: *** No rule to make target 'mm/kpromoted.o', needed by 'mm/built-in.a'. Stop.
***
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 balbirs@nvidia.com bharata@amd.com byungchul@sk.com dave.hansen@intel.com dave@stgolabs.net david@redhat.com gourry@gourry.net hannes@cmpxchg.org jonathan.cameron@huawei.com joshua.hahnjy@gmail.com kinseyho@google.com linux-kernel@vger.kernel.org linux-mm@kvack.org mgorman@techsingularity.net mingo@redhat.com nifan.cxl@gmail.com peterz@infradead.org raghavendra.kt@amd.com riel@surriel.com rientjes@google.com sj@kernel.org weixugc@google.com willy@infradead.org xuezhengchu@huawei.com yiannis@zptcorp.com ying.huang@linux.alibaba.com yuanchu@google.com ziy@nvidia.com]
If the report looks fine to you, reply with:
#syz upstream
reply other threads:[~2025-08-15 16:28 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=689f604a.050a0220.e29e5.001d.GAE@google.com \
--to=syzbot+cia45a30af98595083@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.