From: sashiko-bot@kernel.org
To: "SJ Park" <sj@kernel.org>
Cc: damon@lists.linux.dev
Subject: Re: [PATCH 1/3] mm/damon: add damon_region->last_probe_hits
Date: Fri, 03 Jul 2026 17:24:47 +0000 [thread overview]
Message-ID: <20260703172448.8AE3C1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260703170605.94472-2-sj@kernel.org>
Thank you for your contribution! Sashiko AI review found 3 potential issue(s) to consider:
New issues:
- [Medium] `damos_apply_target()` merges regions without validating or averaging the newly added `last_probe_hits` array.
- [Medium] Missing reset of `probe_hits` when monitoring attributes change dynamically mid-aggregation corrupts the new `last_probe_hits`.
Pre-existing issues:
- [High] `last_nr_accesses` and newly added `last_probe_hits` are not updated or averaged when regions are merged in `damon_merge_two_regions()`.
--
commit 43369d5eda0b4a1301ca211bc77bce0681b92eac
Author: SJ Park <sj@kernel.org>
mm/damon: add damon_region->last_probe_hits
This commit adds a new last_probe_hits array to the damon_region struct.
It maintains fully accumulated probe_hits values from the last aggregation
interval in this new field.
> diff --git a/include/linux/damon.h b/include/linux/damon.h
> index 805e089ff4f2f..4f7e305b261c3 100644
> --- a/include/linux/damon.h
> +++ b/include/linux/damon.h
> @@ -68,10 +68,10 @@ struct damon_region {
> unsigned int nr_accesses;
> unsigned char probe_hits[DAMON_MAX_PROBES];
> struct list_head list;
> -
> unsigned int age;
> /* private: Internal value for age calculation. */
> unsigned int last_nr_accesses;
> + unsigned char last_probe_hits[DAMON_MAX_PROBES];
> };
[Severity: High]
This is a pre-existing issue, but does damon_merge_two_regions() also need
to average last_nr_accesses and this newly added last_probe_hits array?
In mm/damon/core.c:damon_merge_two_regions():
l->nr_accesses = (l->nr_accesses * sz_l + r->nr_accesses * sz_r) /
(sz_l + sz_r);
l->age = (l->age * sz_l + r->age * sz_r) / (sz_l + sz_r);
l->ar.end = r->ar.end;
Because last_nr_accesses and last_probe_hits are left unmodified as the left
region's values, it seems this can cause spurious age resets in later loop
passes. If the left region's last_nr_accesses was 0, but the newly averaged
nr_accesses is non-zero, the condition ((r->nr_accesses == 0) !=
(r->last_nr_accesses == 0)) evaluates to true and spuriously resets r->age
to 0.
[Severity: Medium]
Should this newly added field also be validated in damos_apply_target()?
When damos_apply_target() iterates over regions, it merges adjacent ones if
their age, nr_accesses, and last_nr_accesses match:
if (prev_r->last_nr_accesses != r->last_nr_accesses)
continue;
if (prev_r->nr_accesses != r->nr_accesses)
continue;
Because last_probe_hits isn't compared, regions with different probe statistics
might be erroneously merged, and the right region's probe hits would be
silently discarded.
[ ... ]
> diff --git a/mm/damon/core.c b/mm/damon/core.c
> index c6fc35be633b3..60be3e9d87887 100644
> --- a/mm/damon/core.c
> +++ b/mm/damon/core.c
[ ... ]
> @@ -2040,8 +2042,10 @@ static void kdamond_reset_aggregated(struct damon_ctx *c)
> damon_nr_regions(t), nr_probes);
> r->last_nr_accesses = r->nr_accesses;
> r->nr_accesses = 0;
> - for (i = 0; i < DAMON_MAX_PROBES; i++)
> + for (i = 0; i < DAMON_MAX_PROBES; i++) {
> + r->last_probe_hits[i] = r->probe_hits[i];
> r->probe_hits[i] = 0;
> + }
> }
> ti++;
> }
[Severity: Medium]
Could this copy un-reset, partial-interval probe_hits into last_probe_hits
when monitoring attributes change dynamically?
When damon_set_attrs() dynamically changes intervals mid-aggregation,
damon_update_monitoring_result() explicitly resets nr_accesses to drop the
partial state:
if (!aggregating)
r->nr_accesses = damon_nr_accesses_for_new_attrs(r->nr_accesses,
old_attrs, new_attrs);
else
r->nr_accesses = 0;
However, probe_hits is not reset. When kdamond_reset_aggregated() fires next,
will it populate last_probe_hits with mixed-interval garbage, violating the
fully accumulated semantic guarantee?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260703170605.94472-1-sj@kernel.org?part=1
next prev parent reply other threads:[~2026-07-03 17:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-03 17:06 [PATCH 0/3] mm/damon: provide pseudo moving sum probe_hits SJ Park
2026-07-03 17:06 ` [PATCH 1/3] mm/damon: add damon_region->last_probe_hits SJ Park
2026-07-03 17:24 ` sashiko-bot [this message]
2026-07-03 17:38 ` SJ Park
2026-07-03 17:06 ` [PATCH 2/3] mm/damon/core: introduce damon_probe_hits_mvsum() SJ Park
2026-07-03 17:06 ` [PATCH 3/3] mm/damon/sysfs-schemes: set probe hits as pseudo moving sums SJ Park
2026-07-03 17:26 ` sashiko-bot
2026-07-03 17:42 ` 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=20260703172448.8AE3C1F000E9@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