From: sashiko-bot@kernel.org
To: "SJ Park" <sj@kernel.org>
Cc: damon@lists.linux.dev
Subject: Re: [RFC PATCH v1.3 5/7] mm/damon/core: s/nr_accesses_for_new_attrs/nr_samples_for_new_attrs/
Date: Wed, 08 Jul 2026 03:01:54 +0000 [thread overview]
Message-ID: <20260708030154.C6C441F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260708024855.116614-6-sj@kernel.org>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
Pre-existing issues:
- [High] 32-bit integer overflow in sample scaling functions `damon_sample_bp_to_count` and `damon_sample_count_to_bp`.
--
--- Patch [5]: [RFC PATCH v1.3 5/7] mm/damon/core: s/nr_accesses_for_new_attrs/nr_samples_for_new_attrs/ ---
commit 9db3c90e1f930b4b71612a504362560074396989
Author: SJ Park <sj@kernel.org>
mm/damon/core: s/nr_accesses_for_new_attrs/nr_samples_for_new_attrs/
damon_nr_accesses_for_new_attrs() can be used for not only nr_accesses
but also any positive sample count, like probe_hits. Rename to be able
to be used for such general uses without confusion.
> diff --git a/mm/damon/core.c b/mm/damon/core.c
> index 718268df27fa7..800ff6b6d2473 100644
> --- a/mm/damon/core.c
> +++ b/mm/damon/core.c
> @@ -890,22 +890,21 @@ static unsigned int damon_sample_count_to_bp(
> return mult_frac(count, 10000, damon_nr_samples_per_aggr(attrs));
> }
[Severity: High]
This isn't a bug introduced by this patch, but can the 32-bit unsigned
integer multiplication here and in damon_sample_bp_to_count() overflow?
When a privileged user configures an aggregation to sample interval ratio
greater than ~429,496 via sysfs (e.g., 10s aggregation and 10us sampling),
the mult_frac() macro performs a 32-bit multiplication of the remainder
by 10000. This could overflow when the remainder exceeds 429,496.
Similarly, in damon_sample_bp_to_count():
mm/damon/core.c:damon_sample_bp_to_count() {
...
return bp * damon_nr_samples_per_aggr(attrs) / 10000;
}
The expression bp * damon_nr_samples_per_aggr(attrs) is performed as a
32-bit unsigned int multiplication, which could overflow 4.29B.
Could this overflow silently corrupt region access counts, causing DAMON to
make incorrect memory management decisions like paging out actively used
memory?
>
> -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,
> struct damon_attrs *old_attrs, struct damon_attrs *new_attrs)
> {
> return damon_sample_bp_to_count(
> - damon_sample_count_to_bp(nr_accesses, old_attrs),
> - new_attrs);
> + damon_sample_count_to_bp(nr, old_attrs), new_attrs);
> }
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260708024855.116614-1-sj@kernel.org?part=5
next prev parent reply other threads:[~2026-07-08 3:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 2:48 [RFC PATCH v1.3 0/7] mm/damon: update probe hits for runtime parameter commits SJ Park
2026-07-08 2:48 ` [RFC PATCH v1.3 1/7] mm/damon/core: remove comment and test for nr_to_bp() divide-by-zero SJ Park
2026-07-08 2:48 ` [RFC PATCH v1.3 2/7] mm/damon/core: s/damon_max_nr_accesses()/damon_nr_samples_per_aggr()/ SJ Park
2026-07-08 2:58 ` sashiko-bot
2026-07-08 3:52 ` SJ Park
2026-07-08 2:48 ` [RFC PATCH v1.3 3/7] mm/damon/core: s/accesses_bp_to_nr_accesses/sample_bp_to_count/ SJ Park
2026-07-08 2:48 ` [RFC PATCH v1.3 4/7] mm/damon/core: s/nr_accesses_to_accesses_bp/sample_count_to_bp/ SJ Park
2026-07-08 2:48 ` [RFC PATCH v1.3 5/7] mm/damon/core: s/nr_accesses_for_new_attrs/nr_samples_for_new_attrs/ SJ Park
2026-07-08 3:01 ` sashiko-bot [this message]
2026-07-08 3:53 ` SJ Park
2026-07-08 2:48 ` [RFC PATCH v1.3 6/7] mm/damon/core: update probe hits for new parameter commit SJ Park
2026-07-08 3:05 ` sashiko-bot
2026-07-08 3:56 ` SJ Park
2026-07-08 2:48 ` [RFC PATCH v1.3 7/7] 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=20260708030154.C6C441F000E9@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.