DAMON development mailing list
 help / color / mirror / Atom feed
From: SeongJae Park <sj@kernel.org>
To: sashiko-bot@kernel.org
Cc: SeongJae Park <sj@kernel.org>, damon@lists.linux.dev
Subject: Re: [RFC PATCH v1.3 04/18] mm/damon/core: handle unreset nr_accesses in damon_nr_accesses_mvsum()
Date: Mon, 22 Jun 2026 17:23:12 -0700	[thread overview]
Message-ID: <20260623002313.35582-1-sj@kernel.org> (raw)
In-Reply-To: <20260622144211.CE27A1F000E9@smtp.kernel.org>

On Mon, 22 Jun 2026 14:42:11 +0000 sashiko-bot@kernel.org wrote:

> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Medium] damon_nr_accesses_mvsum() incorrectly returns stale access data from two aggregation intervals ago during the aggregation reset gap.
> --
> 
> commit 079525184ff6b3e5e3e7c3387647af444428cb84
> Author: SeongJae Park <sj@kernel.org>
> 
> mm/damon/core: handle unreset nr_accesses in damon_nr_accesses_mvsum()
> 
> This commit addresses an issue in damon_nr_accesses_mvsum() where unreset
> nr_accesses can unnecessarily inflate the pseudo moving sum. It adds a check
> to return last_nr_accesses directly if the remaining window is full.
> 
> > diff --git a/mm/damon/core.c b/mm/damon/core.c
> > index bc40a6d10f277..8a7351b4a27c2 100644
> > --- a/mm/damon/core.c
> > +++ b/mm/damon/core.c
> > @@ -268,6 +268,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 regression return stale access data from two aggregation intervals
> ago?
> 
> If damon_set_attrs() is executed at the end of an aggregation window, it
> advances ctx->next_aggregation_sis but intentionally does not reset
> r->nr_accesses.
> 
> During this unreset gap, r->nr_accesses correctly retains the fully-aggregated
> data of the just-finished window, while r->last_nr_accesses holds the value
> from two windows ago.
> 
> Because next_aggregation_sis was advanced, left_window_bp evaluates to 10000
> in damon_nr_accesses_mvsum(). Does the new check fall back to the
> stale last_nr_accesses, skipping the most recent interval's data?

Too minor issue.  I will keep this as is, and work on further improvement as I
also mentioned on the commit message.  No blocker for this patch.


Thanks,
SJ

[...]

  reply	other threads:[~2026-06-23  0:23 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-22 14:21 [RFC PATCH v1.3 00/18] mm/damon: optimize out nr_accesses_bp SeongJae Park
2026-06-22 14:21 ` [RFC PATCH v1.3 01/18] mm/damon: introduce damon_nr_accesses_mvsum() SeongJae Park
2026-06-22 14:36   ` sashiko-bot
2026-06-23  0:19     ` SeongJae Park
2026-06-22 14:21 ` [RFC PATCH v1.3 02/18] mm/damon/tests/core-kunit: test damon_mvsum() SeongJae Park
2026-06-22 14:21 ` [RFC PATCH v1.3 03/18] mm/damon/core: always update ->last_nr_accesses for intervals change SeongJae Park
2026-06-22 14:37   ` sashiko-bot
2026-06-23  0:20     ` SeongJae Park
2026-06-22 14:21 ` [RFC PATCH v1.3 04/18] mm/damon/core: handle unreset nr_accesses in damon_nr_accesses_mvsum() SeongJae Park
2026-06-22 14:42   ` sashiko-bot
2026-06-23  0:23     ` SeongJae Park [this message]
2026-06-22 14:21 ` [RFC PATCH v1.3 05/18] mm/damon/core: use damon_nr_accesses_mvsum() in __damos_valid_target() SeongJae Park
2026-06-22 14:37   ` sashiko-bot
2026-06-23  0:24     ` SeongJae Park
2026-06-22 14:21 ` [RFC PATCH v1.3 06/18] mm/damon/core: use damon_nr_accesses_mvsum() for damos region tracing SeongJae Park
2026-06-22 14:21 ` [RFC PATCH v1.3 07/18] mm/damon/sysfs-schemes: use damon_nr_accesses_mvsum() for damo regions SeongJae Park
2026-06-22 14:36   ` sashiko-bot
2026-06-23  0:25     ` SeongJae Park
2026-06-22 14:21 ` [RFC PATCH v1.3 08/18] mm/damon/core: remove damon_warn_fix_nr_accesses_corruption() SeongJae Park
2026-06-22 14:21 ` [RFC PATCH v1.3 09/18] mm/damon/core: remove damon_verify_reset_aggregated() SeongJae Park
2026-06-22 14:21 ` [RFC PATCH v1.3 10/18] mm/damon/core: remove damon_verify_merge_regions_of() SeongJae Park
2026-06-22 14:21 ` [RFC PATCH v1.3 11/18] mm/damon/tests/core-kunit: remove nr_accesses_bp setup and tests SeongJae Park
2026-06-22 14:21 ` [RFC PATCH v1.3 12/18] selftests/damon/drgn_dump_damon_status: do not dump nr_accesses_bp SeongJae Park
2026-06-22 14:21 ` [RFC PATCH v1.3 13/18] mm/damon/core: remove nr_accesses_bp setups and updates SeongJae Park
2026-06-22 14:21 ` [RFC PATCH v1.3 14/18] mm/damon/core: remove attrs param from damon_update_region_access_rate() SeongJae Park
2026-06-22 14:21 ` [RFC PATCH v1.3 15/18] mm/damonn/paddr: remove attrs param from __damon_pa_check_access() SeongJae Park
2026-06-22 14:21 ` [RFC PATCH v1.3 16/18] mm/damon/vaddr: remove attrs param from __damon_va_check_access() SeongJae Park
2026-06-22 14:21 ` [RFC PATCH v1.3 17/18] mm/damon/core: remove damon_moving_sum() and its unit test SeongJae Park
2026-06-22 14:21 ` [RFC PATCH v1.3 18/18] mm/damon: remove damon_region->nr_accesses_bp SeongJae 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=20260623002313.35582-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