From: sashiko-bot@kernel.org
To: "SJ Park" <sj@kernel.org>
Cc: damon@lists.linux.dev
Subject: Re: [RFC PATCH v2.2 12/17] mm/damon/sysfs: implement prep_action file
Date: Tue, 28 Jul 2026 04:23:45 +0000 [thread overview]
Message-ID: <20260728042346.5E3661F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260728041242.187380-13-sj@kernel.org>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The `prep_action` configuration is completely ignored and never applied to the DAMON core.
--
--- Patch [12]: [RFC PATCH v2.2 12/17] mm/damon/sysfs: implement prep_action file ---
commit 5572380654e6a74889b64fc57510a982daf24d8e
Author: SJ Park <sj@kernel.org>
mm/damon/sysfs: implement prep_action file
Add a file named prep_action under the prep directory. It represents
the corresponding probe preparation action.
> diff --git a/mm/damon/sysfs.c b/mm/damon/sysfs.c
> index afd39659d6b84..c0130843223d7 100644
> --- a/mm/damon/sysfs.c
> +++ b/mm/damon/sysfs.c
> @@ -756,6 +756,7 @@ static const struct kobj_type damon_sysfs_intervals_ktype = {
>
> struct damon_sysfs_prep {
> struct kobject kobj;
> + enum damon_prep_action action;
> };
>
> static struct damon_sysfs_prep *damon_sysfs_prep_alloc(void)
[ ... ]
> +static ssize_t prep_action_store(struct kobject *kobj,
> + struct kobj_attribute *attr, const char *buf, size_t count)
> +{
> + struct damon_sysfs_prep *prep = container_of(kobj,
> + struct damon_sysfs_prep, kobj);
> + ssize_t ret = -EINVAL;
> + int i;
> +
> + for (i = 0; i < ARRAY_SIZE(damon_sysfs_prep_action_names); i++) {
> + const struct damon_sysfs_prep_action_name *action_name;
> +
> + action_name = &damon_sysfs_prep_action_names[i];
> + if (sysfs_streq(buf, action_name->name)) {
> + prep->action = action_name->action;
[Severity: Medium]
Are we missing the logic to apply this configuration to the DAMON core?
Looking at damon_sysfs_set_probe(), it commits sysfs configurations to a probe
by calling damon_sysfs_set_filters(), but it appears to skip the preps
directory entirely:
static int damon_sysfs_set_probe(struct damon_probe *probe,
struct damon_sysfs_probe *sys_probe)
{
struct damon_sysfs_filters *sys_filters;
sys_filters = sys_probe->filters;
if (!sys_filters)
return 0;
return damon_sysfs_set_filters(probe, sys_filters);
}
Does this mean the prep_action configuration is never applied when a user
commits the context?
> + ret = count;
> + break;
> + }
> + }
> + return ret;
> +}
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260728041242.187380-1-sj@kernel.org?part=12
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
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 [this message]
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=20260728042346.5E3661F000E9@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