From: SJ Park <sj@kernel.org>
To: sashiko-bot@kernel.org
Cc: SJ Park <sj@kernel.org>, damon@lists.linux.dev
Subject: Re: [RFC PATCH v1.1 06/16] mm/damon/paddr: respect return_max_wsum
Date: Mon, 6 Jul 2026 16:47:52 -0700 [thread overview]
Message-ID: <20260706234754.96945-1-sj@kernel.org> (raw)
In-Reply-To: <20260706144426.157E61F000E9@smtp.kernel.org>
On Mon, 06 Jul 2026 14:44:25 +0000 sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
>
> Pre-existing issues:
> - [High] The `probe_hits` array in `struct damon_region` is of type `unsigned char`, causing silent wrap-around if the number of sampling intervals in an aggregation interval (`aggr_samples`) exceeds 255.
> --
>
> commit d141f3812ddd7e9395e9f362f8ddc5918e7ab555
> Author: SJ Park <sj@kernel.org>
>
> mm/damon/paddr: respect return_max_wsum
>
> apply_probes() ops implementation in DAMON_PADDR is ignoring
> return_max_wsum. Respect it.
>
> > diff --git a/mm/damon/paddr.c b/mm/damon/paddr.c
> > index 3eba3564a31fc..b85f88a7a38f4 100644
> > --- a/mm/damon/paddr.c
> > +++ b/mm/damon/paddr.c
>
> [ ... ]
>
> > @@ -193,9 +193,12 @@ static unsigned int damon_pa_apply_probes(struct damon_ctx *ctx,
> > }
> > if (folio)
> > folio_put(folio);
> > + if (return_max_wsum)
> > + max_wsum = max(damon_probe_hits_wsum(r, false,
> > + ctx), max_wsum);
> > }
> > }
> > - return 0;
> > + return max_wsum;
> > }
>
> [Severity: High]
> This is a pre-existing issue, but I noticed something about the probe_hits
> array while reviewing this area. Does this code silently wrap around if the
> number of samples in an aggregation interval exceeds 255?
>
> Looking at the damon_region structure in include/linux/damon.h, probe_hits
> is defined as an unsigned char array:
>
> include/linux/damon.h:struct damon_region {
> ...
> unsigned char probe_hits[DAMON_MAX_PROBES];
> ...
> };
>
> In mm/damon/paddr.c:damon_pa_apply_probes(), this value is incremented on
> every sampling interval without bounds checking:
>
> mm/damon/paddr.c:damon_pa_apply_probes() {
> ...
> damon_for_each_probe(p, ctx) {
> if (damon_pa_filter_pass(pa, folio, p))
> r->probe_hits[i]++;
> i++;
> }
> ...
> }
>
> If a user configures the sysfs settings such that the aggregation interval
> is significantly larger than the sample interval (for example, a 1ms
> sample interval and a 1s aggregation interval yields 1000 samples), will
> r->probe_hits[i] wrap around and start over from zero?
>
> If so, it appears this might break DAMON region merging and monitoring
> statistics by operating on incorrect, wrapped-around numbers.
Known low priority issue. No blocker.
>
> --
> Sashiko AI review · https://sashiko.dev/#/patchset/20260706141912.88445-1-sj@kernel.org?part=6
Thanks,
SJ
next prev parent reply other threads:[~2026-07-06 23:47 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-06 14:18 [RFC PATCH v1.1 00/16] mm/damon: introduce data attributes only monitoring SJ Park
2026-07-06 14:18 ` [RFC PATCH v1.1 01/16] mm/damon/core: introduce damon_probe->weight SJ Park
2026-07-06 14:18 ` [RFC PATCH v1.1 02/16] mm/damon/core: ask apply_probes() ops callback to set sampling address SJ Park
2026-07-06 14:18 ` [RFC PATCH v1.1 03/16] mm/damon/paddr: set samples in apply_probes() if requested SJ Park
2026-07-06 14:18 ` [RFC PATCH v1.1 04/16] mm/damon/core: ask apply_probe() to return max probe hits weighted sum SJ Park
2026-07-06 14:39 ` sashiko-bot
2026-07-06 23:42 ` SJ Park
2026-07-06 14:18 ` [RFC PATCH v1.1 05/16] mm/damon/core: implement damon_probe_hits_wsum() SJ Park
2026-07-06 14:41 ` sashiko-bot
2026-07-06 23:46 ` SJ Park
2026-07-06 14:19 ` [RFC PATCH v1.1 06/16] mm/damon/paddr: respect return_max_wsum SJ Park
2026-07-06 14:44 ` sashiko-bot
2026-07-06 23:47 ` SJ Park [this message]
2026-07-06 14:19 ` [RFC PATCH v1.1 07/16] mm/damon/core: extend merge function to work with probe hits SJ Park
2026-07-06 14:55 ` sashiko-bot
2026-07-06 23:52 ` SJ Park
2026-07-07 3:30 ` SJ Park
2026-07-06 14:19 ` [RFC PATCH v1.1 08/16] mm/damon/core: disable access monitoring when probe weights are set SJ Park
2026-07-06 15:03 ` sashiko-bot
2026-07-06 23:54 ` SJ Park
2026-07-06 14:19 ` [RFC PATCH v1.1 09/16] mm/damon/core: set samples in apply_probes() if " SJ Park
2026-07-06 15:02 ` sashiko-bot
2026-07-06 23:56 ` SJ Park
2026-07-06 14:19 ` [RFC PATCH v1.1 10/16] mm/damon/core: s/max_nr_accesses/max_merge_score/ in kdamond_fn() SJ Park
2026-07-06 14:19 ` [RFC PATCH v1.1 11/16] mm/damon/core: get merge threshold from probe hits when weights are set SJ Park
2026-07-06 15:18 ` sashiko-bot
2026-07-07 0:03 ` SJ Park
2026-07-07 3:34 ` SJ Park
2026-07-06 14:19 ` [RFC PATCH v1.1 12/16] mm/damon/core: implement damon_has_probe_weight() SJ Park
2026-07-06 15:16 ` sashiko-bot
2026-07-07 0:05 ` SJ Park
2026-07-06 14:19 ` [RFC PATCH v1.1 13/16] mm/damon/sysfs: implement probe/weight file SJ Park
2026-07-06 15:19 ` sashiko-bot
2026-07-07 0:08 ` SJ Park
2026-07-06 14:19 ` [RFC PATCH v1.1 14/16] Docs/mm/damon/design: document attrs-only monitoring SJ Park
2026-07-06 15:34 ` sashiko-bot
2026-07-07 0:11 ` SJ Park
2026-07-06 14:19 ` [RFC PATCH v1.1 15/16] Docs/admin-guide/mm/damon/usage: document weight sysfs file SJ Park
2026-07-06 14:19 ` [RFC PATCH v1.1 16/16] Docs/ABI/damon: document probe weight file SJ Park
2026-07-07 0:13 ` [RFC PATCH v1.1 00/16] mm/damon: introduce data attributes only monitoring 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=20260706234754.96945-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=damon@lists.linux.dev \
--cc=sashiko-bot@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