DAMON development mailing list
 help / color / mirror / Atom feed
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 4/6] mm/damon/core: s/nr_accesses_for_new_attrs/nr_samples_for_new_attrs/
Date: Mon,  6 Jul 2026 22:08:23 -0700	[thread overview]
Message-ID: <20260707050825.102567-1-sj@kernel.org> (raw)
In-Reply-To: <20260707045018.C227B1F000E9@smtp.kernel.org>

On Tue, 07 Jul 2026 04:50:18 +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] 32-bit integer overflow in damon_sample_bp_to_count() and damon_sample_count_to_bp() corrupts memory access tracking.
> --
> 
> --- Patch [4]: [RFC PATCH 4/6] mm/damon/core: s/nr_accesses_for_new_attrs/nr_samples_for_new_attrs/ ---
> commit cb8a54b34f772f70862ab31ccf30eea4a5cb2263
> Author: SJ Park <sj@kernel.org>
> 
> mm/damon/core: s/nr_accesses_for_new_attrs/nr_samples_for_new_attrs/
> 
> This commit renames damon_nr_accesses_for_new_attrs() to
> damon_nr_samples_for_new_attrs() to clarify its general use for any
> positive sample count.
> 
> > diff --git a/mm/damon/core.c b/mm/damon/core.c
> > index 718268df27fa7..cda318806b65b 100644
> > --- a/mm/damon/core.c
> > +++ b/mm/damon/core.c
> > @@ -890,7 +890,7 @@ static unsigned int damon_sample_count_to_bp(
> >  	return mult_frac(count, 10000, damon_nr_samples_per_aggr(attrs));
> >  }
> >  
> 
> [Severity: High]
> This is a pre-existing issue, but can this math silently overflow when the
> sample count is large?
> 
> In mm/damon/core.c:damon_sample_count_to_bp(), the mult_frac() macro inherits
> the 32-bit precision of 'count'. If the user configures sysfs such that max
> samples exceeds ~429,496, the intermediate remainder multiplication can wrap
> around UINT_MAX.
> 
> For instance, 450,000 accesses out of 500,000 maximum samples will silently
> overflow during mult_frac() calculation, resulting in a basis point of 410
> (4.1% hot) instead of 9000 (90% hot).
> 
> Similarly, in mm/damon/core.c:damon_sample_bp_to_count():
> 
>     static unsigned int damon_sample_bp_to_count(
>             unsigned int bp, struct damon_attrs *attrs)
>     {
>         return bp * damon_nr_samples_per_aggr(attrs) / 10000;
>     }
> 
> The multiplication occurs in 32-bit precision before the division by 10000.
> If damon_nr_samples_per_aggr() exceeds ~429,496, this will also overflow.
> 
> This drastic corruption could cause DAMOS to incorrectly evaluate region
> hotness, potentially swapping out highly accessed memory. Would it make sense
> to cast these to a 64-bit type before multiplication to avoid the overflow?

Known low priority issue.

> 
> > -static unsigned int damon_nr_accesses_for_new_attrs(unsigned int nr_accesses,
> > +static unsigned int damon_nr_samples_for_new_attrs(unsigned int nr_accesses,
> >  		struct damon_attrs *old_attrs, struct damon_attrs *new_attrs)
> >  {
> >  	return damon_sample_bp_to_count(
> 
> [ ... ]
> 
> -- 
> Sashiko AI review · https://sashiko.dev/#/patchset/20260707043828.97900-1-sj@kernel.org?part=4


Thanks,
SJ

[...]

  reply	other threads:[~2026-07-07  5:08 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-07  4:38 [RFC PATCH 0/6] mm/damon: update probe hits for runtime parameter commits SJ Park
2026-07-07  4:38 ` [RFC PATCH 1/6] mm/damon/core: s/damon_max_nr_accesses()/damon_nr_samples_per_aggr()/ SJ Park
2026-07-07  4:48   ` sashiko-bot
2026-07-07  5:01     ` SJ Park
2026-07-07  4:38 ` [RFC PATCH 2/6] mm/damon/core: s/accesses_bp_to_nr_accesses/sample_bp_to_count/ SJ Park
2026-07-07  4:49   ` sashiko-bot
2026-07-07  5:02     ` SJ Park
2026-07-07  4:38 ` [RFC PATCH 3/6] mm/damon/core: s/nr_accesses_to_accesses_bp/sample_count_to_bp/ SJ Park
2026-07-07  4:45   ` sashiko-bot
2026-07-07  5:07     ` SJ Park
2026-07-07  4:38 ` [RFC PATCH 4/6] mm/damon/core: s/nr_accesses_for_new_attrs/nr_samples_for_new_attrs/ SJ Park
2026-07-07  4:50   ` sashiko-bot
2026-07-07  5:08     ` SJ Park [this message]
2026-07-07  4:38 ` [RFC PATCH 5/6] mm/damon/core: update probe hits for new parameter commit SJ Park
2026-07-07  4:51   ` sashiko-bot
2026-07-07  5:09     ` SJ Park
2026-07-07  4:38 ` [RFC PATCH 6/6] mm/damon/core: handle unreset probe_hits in probe_hits_mvsum() 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=20260707050825.102567-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