From: syzbot ci <syzbot+cid6635130a31bd54c@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: mm/damon: misc improvements/cleanups for core, vaddr, sysfs and tests
Date: Sun, 01 Nov 2026 16:59:57 -0800 [thread overview]
Message-ID: <6ae7e08d.6552420f.2a0efc.00b1.GAE@google.com> (raw)
syzbot ci has tested the following series
[v2] mm/damon: misc improvements/cleanups for core, vaddr, sysfs and tests
https://lore.kernel.org/all/20261101171630.81477-1-sj@kernel.org
* [RFC PATCH v2 1/6] mm/damon/vaddr: advance migration attempt in folio level for filter out
* [RFC PATCH v2 2/6] mm/damon/vaddr: use damos->last_applied for migrate action
* [RFC PATCH v2 3/6] mm/damon/vaddr: implement sz_filter_passed for migrate_{hot,cold} action
* [RFC PATCH v2 4/6] mm/damon/sysfs-schemes: drop redundant and racy zero target_value check
* [RFC PATCH v2 5/6] selftests/damon/damos_apply_interval: remove unused variables
* [RFC PATCH v2 6/6] selftests/damon: remove unused imports of os and sys modules
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/71de7a4b-c1c2-42ca-bb10-eea627deddc0
***
kernel build error
tree: mm-new
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/akpm/mm.git
base: 243e8cdab64129d6207c398f8cf5fbb1962ff7e1
arch: amd64
compiler: Debian clang version 22.1.8 (1~deb13u4), Debian LLD 22.1.8
config: https://ci.syzbot.org/builds/f7c3cdf7-8d33-4608-b26d-34f4cae5dcfa/config
mm/damon/vaddr.c:870:54: error: use of undeclared identifier 'dests'
mm/damon/vaddr.c:899:54: error: use of undeclared identifier 'dests'
***
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.
To test a fix for this bug, please reply with `#syz test`
(on a separate line) and attach the patch to the email.
Notes:
- The patch will be applied on top of the tested series (as an
incremental fix).
- To test a new version of the whole series, please send it directly
to syzbot@lists.linux.dev.
- Arguments like custom git repos and branches are not supported.
The email will later be sent to:
[akpm@linux-foundation.org damon@lists.linux.dev linux-kernel@vger.kernel.org linux-kselftest@vger.kernel.org linux-mm@kvack.org shuah@kernel.org sj@kernel.org]
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-11-02 0:59 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=6ae7e08d.6552420f.2a0efc.00b1.GAE@google.com \
--to=syzbot+cid6635130a31bd54c@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