public inbox for linux-mm@kvack.org
 help / color / mirror / Atom feed
From: SeongJae Park <sj@kernel.org>
To: SeongJae Park <sj@kernel.org>
Cc: Shuah Khan <shuah@kernel.org>,
	damon@lists.linux.dev, linux-kernel@vger.kernel.org,
	linux-kselftest@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [RFC PATCH 10/10] selftets/damon/sysfs.py: pause DAMON before dumping status
Date: Mon, 16 Mar 2026 21:34:28 -0700	[thread overview]
Message-ID: <20260317043429.1057-1-sj@kernel.org> (raw)
In-Reply-To: <20260315210012.94846-11-sj@kernel.org>

On Sun, 15 Mar 2026 14:00:09 -0700 SeongJae Park <sj@kernel.org> wrote:

> The sysfs.py test commits DAMON parameters, dump the internal DAMON
> state, and show if the parameters are committed as expected using the
> dumped state.  While the dumping is ongoing, DAMON is alive.  It can
> make internal changes including addition and removal of regions.  It can
> therefore make a race that can result in false test results.  Pause
> DAMON execution during the state dumping to avoid such races.
> 
> Signed-off-by: SeongJae Park <sj@kernel.org>
> ---
>  tools/testing/selftests/damon/sysfs.py | 27 ++++++++++++++++++++++++++
>  1 file changed, 27 insertions(+)
> 
> diff --git a/tools/testing/selftests/damon/sysfs.py b/tools/testing/selftests/damon/sysfs.py
> index e6d34ba05893f..a1a29f1a7c27b 100755
> --- a/tools/testing/selftests/damon/sysfs.py
> +++ b/tools/testing/selftests/damon/sysfs.py
> @@ -193,18 +193,44 @@ def assert_ctx_committed(ctx, dump):
>      assert_true(dump['pause'] == ctx.pause, 'pause', dump)
>  
>  def assert_ctxs_committed(kdamonds):
> +    paused_for_dump = False
> +    if kdamonds.kdamonds[0].contexts[0].pause is False:
> +        kdamonds.kdamonds[0].contexts[0].pause = True

Quoting sashiko.dev comments [1] with ': ' prefix below.

: Does this code only pause the first context? The validation loop below
: iterates over all contexts in the kdamond, so if there are multiple
: contexts, will the others remain unpaused and vulnerable to the race
: condition during the state dump?

There is no real caller of this function that uses multiple contexts.  So there
is no real problem.  That said, I think this code will be better to take care
of such case that might happen in the future.

I will therefore add below change to the next version of this patch.

'''
--- a/tools/testing/selftests/damon/sysfs.py
+++ b/tools/testing/selftests/damon/sysfs.py
@@ -196,15 +196,17 @@ def assert_ctx_committed(ctx, dump):
     assert_true(dump['pause'] == ctx.pause, 'pause', dump)

 def assert_ctxs_committed(kdamonds):
-    paused_for_dump = False
-    if kdamonds.kdamonds[0].contexts[0].pause is False:
-        kdamonds.kdamonds[0].contexts[0].pause = True
-        err = kdamonds.kdamonds[0].commit()
-        if err is not None:
-            print('pause fail (%s)' % err)
-            kdamonds.stop()
-            exit(1)
-        paused_for_dump = True
+    ctxs_paused_for_dump = []
+    for kd in kdamonds.kdamonds:
+        for ctx in kd.contexts:
+            if ctx.pause is False:
+                ctx.pause = True
+                err = kd.commit()
+                if err is not None:
+                    print('pause fail (%s)' % err)
+                    kdamonds.stop()
+                    exit(1)
+                ctxs_paused_for_dump.append(ctx)

     status, err = dump_damon_status_dict(kdamonds.kdamonds[0].pid)
     if err is not None:
@@ -212,17 +214,17 @@ def assert_ctxs_committed(kdamonds):
         kdamonds.stop()
         exit(1)

-    if paused_for_dump:
-        # resume
-        kdamonds.kdamonds[0].contexts[0].pause = False
-        err = kdamonds.kdamonds[0].commit()
-        if err is not None:
-            print('resume fail (%s)' % err)
-            kdamonds.stop()
-            exit(1)
-
-        # restore for comparison
-        kdamonds.kdamonds[0].contexts[0].pause = True
+    for kd in kdamonds.kdamonds:
+        for ctx in kd.contexts:
+            if ctx in ctxs_paused_for_dump:
+                ctx.pause = False
+                err = kd.commit()
+                if err is not None:
+                    print('resume fail (%s)' % err)
+                    kdamonds.stop()
+                    exit(1)
+                # restore for comparison
+                ctx.pause = True

     ctxs = kdamonds.kdamonds[0].contexts
     dump = status['contexts']
@@ -230,9 +232,11 @@ def assert_ctxs_committed(kdamonds):
     for idx, ctx in enumerate(ctxs):
         assert_ctx_committed(ctx, dump[idx])

-    if paused_for_dump:
-        # restore for the caller
-        kdamonds.kdamonds[0].contexts[0].pause = False
+    # restore for the caller
+    for kd in kdamonds.kdamonds:
+        for ctx in kd.contexts:
+            if ctx in ctxs_paused_for_dump:
+                ctx.pause = False

 def main():
     global kdamonds
'''

> +        err = kdamonds.kdamonds[0].commit()

: Does calling commit() here inadvertently mask test failures by forcing the
: entire Python object state to the kernel right before reading the status?
: 
: For example, if a test marks a target obsolete, commits it, and deletes
: the target from the Python list to verify if the kernel autonomously
: removed it, this commit() would explicitly push the target's deletion to
: the kernel, potentially bypassing the test's purpose.

No.  Callers that could have such problem should call this function after
pausing the context on their own.  That's what the target obsolete test case is
doing.

[1] https://sashiko.dev/#/patchset/20260315210012.94846-11-sj@kernel.org


Thanks,
SJ

[...]


      reply	other threads:[~2026-03-17  4:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-15 20:59 [RFC PATCH 00/10] mm/damon: let DAMON be paused and resumed SeongJae Park
2026-03-15 21:00 ` [RFC PATCH 01/10] mm/damon/core: introduce damon_ctx->paused SeongJae Park
2026-03-17  4:20   ` SeongJae Park
2026-03-15 21:00 ` [RFC PATCH 02/10] mm/damon/sysfs: add pause file under context dir SeongJae Park
2026-03-17  4:26   ` SeongJae Park
2026-03-15 21:00 ` [RFC PATCH 03/10] Docs/mm/damon/design: update for context pause/resume feature SeongJae Park
2026-03-15 21:00 ` [RFC PATCH 04/10] Docs/admin-guide/mm/damon/usage: update for pause file SeongJae Park
2026-03-15 21:00 ` [RFC PATCH 05/10] Docs/ABI/damon: update for pause sysfs file SeongJae Park
2026-03-15 21:00 ` [RFC PATCH 06/10] mm/damon/tests/core-kunit: test pause commitment SeongJae Park
2026-03-15 21:00 ` [RFC PATCH 07/10] selftests/damon/_damon_sysfs: support pause file staging SeongJae Park
2026-03-15 21:00 ` [RFC PATCH 08/10] selftests/damon/drgn_dump_damon_status: dump pause SeongJae Park
2026-03-15 21:00 ` [RFC PATCH 09/10] selftests/damon/sysfs.py: check pause on assert_ctx_committed() SeongJae Park
2026-03-15 21:00 ` [RFC PATCH 10/10] selftets/damon/sysfs.py: pause DAMON before dumping status SeongJae Park
2026-03-17  4:34   ` 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=20260317043429.1057-1-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=damon@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=shuah@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