From: syzbot ci <syzbot+cie3db188b2cb17c93@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: support batched checking of the young flag for MGLRU
Date: Fri, 06 Mar 2026 15:58:01 -0800 [thread overview]
Message-ID: <69ab6a09.050a0220.13f275.002f.GAE@google.com> (raw)
syzbot ci has tested the following series
[v3] support batched checking of the young flag for MGLRU
https://lore.kernel.org/all/cover.1772778858.git.baolin.wang@linux.alibaba.com
* [PATCH v3 1/6] mm: use inline helper functions instead of ugly macros
* [PATCH v3 2/6] mm: rename ptep/pmdp_clear_young_notify() to ptep/pmdp_test_and_clear_young_notify()
* [PATCH v3 3/6] mm: rmap: add a ZONE_DEVICE folio warning in folio_referenced()
* [PATCH v3 4/6] mm: add a batched helper to clear the young flag for large folios
* [PATCH v3 5/6] mm: support batched checking of the young flag for MGLRU
* [PATCH v3 6/6] arm64: mm: implement the architecture-specific test_and_clear_young_ptes()
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/ec7a1ad8-d7a8-4ed6-b974-1498b7645030
***
kernel build error
tree: torvalds
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux
base: 5ee8dbf54602dc340d6235b1d6aa17c0f283f48c
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/ca01dc5a-e9c9-424a-9902-c53133976f64/config
mm/damon/ops-common.c:93:12: error: call to undeclared function 'pmdp_clear_young_notify'; 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 axelrasmussen@google.com baohua@kernel.org baolin.wang@linux.alibaba.com catalin.marinas@arm.com david@kernel.org dev.jain@arm.com hannes@cmpxchg.org harry.yoo@oracle.com jannh@google.com liam.howlett@oracle.com linux-arm-kernel@lists.infradead.org linux-kernel@vger.kernel.org linux-mm@kvack.org lorenzo.stoakes@oracle.com mhocko@suse.com riel@surriel.com rppt@kernel.org ryan.roberts@arm.com shakeel.butt@linux.dev surenb@google.com vbabka@suse.cz weixugc@google.com will@kernel.org willy@infradead.org yuanchu@google.com zhengqi.arch@bytedance.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-06 23:58 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=69ab6a09.050a0220.13f275.002f.GAE@google.com \
--to=syzbot+cie3db188b2cb17c93@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