From: SeongJae Park <sj@kernel.org>
To: sashiko-bot@kernel.org
Cc: SeongJae Park <sj@kernel.org>, damon@lists.linux.dev
Subject: Re: [PATCH v2 10/10] selftests/damon/sysfs.py: pause DAMON before dumping status
Date: Mon, 27 Apr 2026 17:22:45 -0700 [thread overview]
Message-ID: <20260428002246.112905-1-sj@kernel.org> (raw)
In-Reply-To: <20260427210420.12AEDC2BCB6@smtp.kernel.org>
On Mon, 27 Apr 2026 21:04:19 +0000 sashiko-bot@kernel.org wrote:
> Sashiko AI review found 1 potential issue(s):
> - [Medium] Mutating the state before assertion bypasses the verification of the original `pause` state.
Not a blocker of this patch in my opinion. Please read below for more details.
> --
>
> commit 2c32bc147a1cb335e85629e00bb0efe1bbb44638
> Author: SeongJae Park <sj@kernel.org>
>
> selftests/damon/sysfs.py: pause DAMON before dumping status
>
> This commit updates the DAMON sysfs selftest to pause DAMON execution
> during state dumping. It attempts to prevent race conditions where DAMON
> could add or remove regions while the dump is ongoing.
>
> > diff --git a/tools/testing/selftests/damon/sysfs.py b/tools/testing/selftests/damon/sysfs.py
> > index e6d34ba05893..b8d6e0f8fd90 100755
> > --- a/tools/testing/selftests/damon/sysfs.py
> > +++ b/tools/testing/selftests/damon/sysfs.py
> > @@ -193,18 +193,55 @@ def assert_ctx_committed(ctx, dump):
> > assert_true(dump['pause'] = ctx.pause, 'pause', dump)
> >
> > def assert_ctxs_committed(kdamonds):
> > + ctxs_paused_for_dump = []
> > + kdamonds_paused_for_dump = []
> > + # pause for safe state dumping
> > + for kd in kdamonds.kdamonds:
> > + for ctx in kd.contexts:
> > + if ctx.pause is False:
> > + ctx.pause = True
> > + ctxs_paused_for_dump.append(ctx)
> > + if not kd in kdamonds_paused_for_dump:
> > + kdamonds_paused_for_dump.append(kd)
> > + if kd in kdamonds_paused_for_dump:
> > + err = kd.commit()
>
> [ ... ]
>
> > + # restore for comparison
> > + for ctx in ctxs_paused_for_dump:
> > + ctx.pause = True
> > +
> > ctxs = kdamonds.kdamonds[0].contexts
> > dump = status['contexts']
> > assert_true(len(ctxs) = len(dump), 'ctxs length', dump)
> > for idx, ctx in enumerate(ctxs):
> > assert_ctx_committed(ctx, dump[idx])
>
> Does this bypass the verification of the original pause state?
>
> By temporarily pausing the DAMON context and committing this new state
> before dumping the sysfs status, the test overwrites the actual pause state
> in the kernel. Then, setting the Python object's ctx.pause to True for
> comparison means the test always compares True against True for the pause
> parameter.
>
> Because of this, the test seems fundamentally incapable of verifying
> whether a pause = False configuration was ever correctly committed to the
> kernel prior to calling assert_ctxs_committed().
This is an intended behavior as I explained in a previous version. We are
using pause for testing. Testing something that being used for testing with
the test itself is complicated. It would be good to have a test for the
feature for the test itself in a way, but not necessarily by the test the
feature is helping for. We have at least pause parameter commit kunit. So I
think this is not a blocker of this patch.
Thanks,
SJ
[...]
prev parent reply other threads:[~2026-04-28 0:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-27 15:12 [PATCH v2 00/10] mm/damon: let DAMON be paused and resumed SeongJae Park
2026-04-27 15:12 ` [PATCH v2 01/10] mm/damon/core: introduce damon_ctx->paused SeongJae Park
2026-04-27 15:12 ` [PATCH v2 02/10] mm/damon/sysfs: add pause file under context dir SeongJae Park
2026-04-27 15:12 ` [PATCH v2 03/10] Docs/mm/damon/design: update for context pause/resume feature SeongJae Park
2026-04-27 15:12 ` [PATCH v2 04/10] Docs/admin-guide/mm/damon/usage: update for pause file SeongJae Park
2026-04-27 15:12 ` [PATCH v2 05/10] Docs/ABI/damon: update for pause sysfs file SeongJae Park
2026-04-27 15:12 ` [PATCH v2 06/10] mm/damon/tests/core-kunit: test pause commitment SeongJae Park
2026-04-27 15:12 ` [PATCH v2 07/10] selftests/damon/_damon_sysfs: support pause file staging SeongJae Park
2026-04-27 15:12 ` [PATCH v2 08/10] selftests/damon/drgn_dump_damon_status: dump pause SeongJae Park
2026-04-27 15:12 ` [PATCH v2 09/10] selftests/damon/sysfs.py: check pause on assert_ctx_committed() SeongJae Park
2026-04-27 15:12 ` [PATCH v2 10/10] selftests/damon/sysfs.py: pause DAMON before dumping status SeongJae Park
2026-04-27 21:04 ` sashiko-bot
2026-04-28 0:22 ` SeongJae Park [this message]
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=20260428002246.112905-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