From: sashiko-bot@kernel.org
To: "SJ Park" <sj@kernel.org>
Cc: damon@lists.linux.dev
Subject: Re: [RFC PATCH v2.2 01/17] mm/damon/core: introduce DAMON_FILTER_TYPE_PGIDLE_UNSET
Date: Tue, 28 Jul 2026 04:23:24 +0000 [thread overview]
Message-ID: <20260728042325.68FB51F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260728041242.187380-2-sj@kernel.org>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The newly introduced DAMON_FILTER_TYPE_PGIDLE_UNSET enum is unhandled in the filter matching logic and sysfs interface, leaving the promised functionality completely missing.
--
--- Patch [1]: [RFC PATCH v2.2 01/17] mm/damon/core: introduce DAMON_FILTER_TYPE_PGIDLE_UNSET ---
commit 1ede3c3f87a9caeeb7ad80090cbb84d20b477505
Author: SJ Park <sj@kernel.org>
mm/damon/core: introduce DAMON_FILTER_TYPE_PGIDLE_UNSET
Introduce a new DAMON filter type, pgidle_unset. It will match pages
that have their PG_Idle flag unset, or the page table accessed bit set.
> diff --git a/include/linux/damon.h b/include/linux/damon.h
> index 0c8b7ddef9abb..a8bb9ee6979e3 100644
> --- a/include/linux/damon.h
> +++ b/include/linux/damon.h
> @@ -742,12 +742,14 @@ struct damon_intervals_goal {
> /**
> * enum damon_filter_type - Type of &struct damon_filter
> *
> - * @DAMON_FILTER_TYPE_ANON: Anonymous pages.
> - * @DAMON_FILTER_TYPE_MEMCG: Specific memcg's pages.
> + * @DAMON_FILTER_TYPE_ANON: Anonymous pages.
> + * @DAMON_FILTER_TYPE_MEMCG: Specific memcg's pages.
> + * @DAMON_FILTER_TYPE_PGIDLE_UNSET: Pgidle is unset.
> */
> enum damon_filter_type {
> DAMON_FILTER_TYPE_ANON,
> DAMON_FILTER_TYPE_MEMCG,
> + DAMON_FILTER_TYPE_PGIDLE_UNSET,
[Severity: Medium]
Is the implementation for this new filter type missing from this patch?
Looking at damon_pa_filter_match() in mm/damon/paddr.c, the switch
statement evaluating filter types does not appear to handle
DAMON_FILTER_TYPE_PGIDLE_UNSET. This means it will fall through to the
default case and fail to implement the promised page matching logic:
mm/damon/paddr.c:damon_pa_filter_match() {
...
switch (filter->type) {
case DAMON_FILTER_TYPE_ANON:
...
}
}
Additionally, it looks like this new filter type is missing from the sysfs
name mapping array, damon_sysfs_filter_type_names, in mm/damon/sysfs.c:
mm/damon/sysfs.c:damon_sysfs_filter_type_names {
{
.type = DAMON_FILTER_TYPE_ANON,
.name = "anon",
},
...
}
Without this mapping, type_store() will fail with -EINVAL, making it
impossible for userspace to configure.
Will a follow-up patch add the handling logic and sysfs bindings, or should
they be included directly in this commit?
> };
>
> /**
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260728041242.187380-1-sj@kernel.org?part=1
next prev parent reply other threads:[~2026-07-28 4:23 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-28 4:12 [RFC PATCH v2.2 00/17] mm/damon: introduce data access-as-a-data attribute SJ Park
2026-07-28 4:12 ` [RFC PATCH v2.2 01/17] mm/damon/core: introduce DAMON_FILTER_TYPE_PGIDLE_UNSET SJ Park
2026-07-28 4:23 ` sashiko-bot [this message]
2026-07-28 4:49 ` SJ Park
2026-07-28 4:12 ` [RFC PATCH v2.2 02/17] mm/damon/paddr: support PGIDLE_UNSET probe filter type SJ Park
2026-07-28 4:32 ` sashiko-bot
2026-07-28 4:52 ` SJ Park
2026-07-28 4:12 ` [RFC PATCH v2.2 03/17] mm/damon/sysfs: support pgidle_unset " SJ Park
2026-07-28 4:12 ` [RFC PATCH v2.2 04/17] Docs/mm/damon/design: document " SJ Park
2026-07-28 4:12 ` [RFC PATCH v2.2 05/17] mm/damon/core: introduce damon_prep struct SJ Park
2026-07-28 4:25 ` sashiko-bot
2026-07-28 4:54 ` SJ Park
2026-07-28 4:12 ` [RFC PATCH v2.2 06/17] mm/damon/core: commit preps SJ Park
2026-07-28 4:12 ` [RFC PATCH v2.2 07/17] mm/damon/core: introduce damon_operations->prep_probes() SJ Park
2026-07-28 4:12 ` [RFC PATCH v2.2 08/17] mm/damon/paddr: support damon_prep SJ Park
2026-07-28 4:24 ` sashiko-bot
2026-07-28 4:56 ` SJ Park
2026-07-28 4:12 ` [RFC PATCH v2.2 09/17] mm/damon/sysfs: implement preps directory SJ Park
2026-07-28 4:12 ` [RFC PATCH v2.2 10/17] mm/damon/sysfs: implement preps/nr_preps file SJ Park
2026-07-28 4:12 ` [RFC PATCH v2.2 11/17] mm/damon/sysfs: create directories for nr_preps writes SJ Park
2026-07-28 4:12 ` [RFC PATCH v2.2 12/17] mm/damon/sysfs: implement prep_action file SJ Park
2026-07-28 4:23 ` sashiko-bot
2026-07-28 4:58 ` SJ Park
2026-07-28 4:12 ` [RFC PATCH v2.2 13/17] mm/damon/sysfs: pass preps to DAMON core SJ Park
2026-07-28 4:12 ` [RFC PATCH v2.2 14/17] selftests/damon/sysfs.sh: test probe prep sysfs files SJ Park
2026-07-28 4:12 ` [RFC PATCH v2.2 15/17] Docs/mm/damon/design: document probe preps SJ Park
2026-07-28 4:12 ` [RFC PATCH v2.2 16/17] Docs/admin-guide/mm/damon/usage: document probe preps sysfs files SJ Park
2026-07-28 4:12 ` [RFC PATCH v2.2 17/17] Docs/ABI/damon: document probe prep " SJ Park
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=20260728042325.68FB51F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=damon@lists.linux.dev \
--cc=sashiko-reviews@lists.linux.dev \
--cc=sj@kernel.org \
/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