From: sashiko-bot@kernel.org
To: "SJ Park" <sj@kernel.org>
Cc: damon@lists.linux.dev
Subject: Re: [PATCH 04/18] mm/damon/core: handle unreset nr_accesses in damon_nr_accesses_mvsum()
Date: Tue, 30 Jun 2026 04:23:36 +0000 [thread overview]
Message-ID: <20260630042337.2F8CE1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260630040812.149729-5-sj@kernel.org>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] damon_nr_accesses_mvsum() incorrectly returns stale data (r->last_nr_accesses) when damon_set_attrs() is called exactly at the end of an aggregation window.
--
commit ebe6cc65ba2de465cab83d7ffe913bb9f8304f66
Author: SJ Park <sj@kernel.org>
mm/damon/core: handle unreset nr_accesses in damon_nr_accesses_mvsum()
This commit adds logic to damon_nr_accesses_mvsum() to return
last_nr_accesses when the remaining window is full. It aims to avoid
unnecessarily counting unreset nr_accesses when damon_set_attrs() is
called at the end of an aggregation window.
> diff --git a/mm/damon/core.c b/mm/damon/core.c
> index 94dd425ee4353..df79f4d10bdc3 100644
> --- a/mm/damon/core.c
> +++ b/mm/damon/core.c
> @@ -266,6 +266,9 @@ unsigned int damon_nr_accesses_mvsum(struct damon_region *r,
> ctx->passed_sample_intervals;
> left_window_bp = mult_frac(left_window, 10000, window_len);
>
> + if (left_window_bp == 10000)
> + return r->last_nr_accesses;
> +
[Severity: Medium]
Will this early return cause the function to return stale data from the
previous window instead of freshly accumulated data?
If damon_set_attrs() is called at the end of an aggregation window,
damon_update_monitoring_result() processes this with aggregating = false.
This intentionally preserves the fully accumulated r->nr_accesses for the
newly completed window.
After damon_set_attrs() pushes ctx->next_aggregation_sis forward, a
subsequent call to damon_nr_accesses_mvsum() will calculate left_window_bp
as 10000.
Because of this early return, won't it discard the freshly accumulated
r->nr_accesses and incorrectly return the older r->last_nr_accesses instead?
> return damon_mvsum(r->nr_accesses, r->last_nr_accesses,
> left_window_bp);
> }
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260630040812.149729-1-sj@kernel.org?part=4
next prev parent reply other threads:[~2026-06-30 4:23 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-30 4:07 [PATCH 00/18] mm/damon: optimize out nr_accesses_bp SJ Park
2026-06-30 4:07 ` [PATCH 01/18] mm/damon/core: introduce damon_nr_accesses_mvsum() SJ Park
2026-06-30 4:19 ` sashiko-bot
2026-06-30 4:28 ` SJ Park
2026-06-30 4:07 ` [PATCH 02/18] mm/damon/tests/core-kunit: test damon_mvsum() SJ Park
2026-06-30 4:07 ` [PATCH 03/18] mm/damon/core: always update ->last_nr_accesses for intervals change SJ Park
2026-06-30 4:21 ` sashiko-bot
2026-06-30 4:30 ` SJ Park
2026-06-30 4:07 ` [PATCH 04/18] mm/damon/core: handle unreset nr_accesses in damon_nr_accesses_mvsum() SJ Park
2026-06-30 4:23 ` sashiko-bot [this message]
2026-06-30 4:33 ` SJ Park
2026-06-30 4:07 ` [PATCH 05/18] mm/damon/core: use damon_nr_accesses_mvsum() in __damos_valid_target() SJ Park
2026-06-30 4:25 ` sashiko-bot
2026-06-30 4:34 ` SJ Park
2026-06-30 4:07 ` [PATCH 06/18] mm/damon/core: use damon_nr_accesses_mvsum() for damos region tracing SJ Park
2026-06-30 4:08 ` [PATCH 07/18] mm/damon/sysfs-schemes: use damon_nr_accesses_mvsum() for damo regions SJ Park
2026-06-30 4:08 ` [PATCH 08/18] mm/damon/core: remove damon_warn_fix_nr_accesses_corruption() SJ Park
2026-06-30 4:08 ` [PATCH 09/18] mm/damon/core: remove damon_verify_reset_aggregated() SJ Park
2026-06-30 4:08 ` [PATCH 10/18] mm/damon/core: remove damon_verify_merge_regions_of() SJ Park
2026-06-30 4:08 ` [PATCH 11/18] mm/damon/tests/core-kunit: remove nr_accesses_bp setup and tests SJ Park
2026-06-30 4:08 ` [PATCH 12/18] selftests/damon/drgn_dump_damon_status: do not dump nr_accesses_bp SJ Park
2026-06-30 4:08 ` [PATCH 13/18] mm/damon/core: remove nr_accesses_bp setups and updates SJ Park
2026-06-30 4:08 ` [PATCH 14/18] mm/damon/core: remove attrs param from damon_update_region_access_rate() SJ Park
2026-06-30 4:19 ` sashiko-bot
2026-06-30 4:39 ` SJ Park
2026-06-30 4:48 ` SJ Park
2026-06-30 4:08 ` [PATCH 15/18] mm/damon/paddr: remove attrs param from __damon_pa_check_access() SJ Park
2026-06-30 4:08 ` [PATCH 16/18] mm/damon/vaddr: remove attrs param from __damon_va_check_access() SJ Park
2026-06-30 4:22 ` sashiko-bot
2026-06-30 4:45 ` SJ Park
2026-06-30 4:08 ` [PATCH 17/18] mm/damon/core: remove damon_moving_sum() and its unit test SJ Park
2026-06-30 4:08 ` [PATCH 18/18] mm/damon/core: remove damon_region->nr_accesses_bp SJ Park
2026-06-30 4:52 ` [PATCH 00/18] mm/damon: optimize out nr_accesses_bp 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=20260630042337.2F8CE1F000E9@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