From: sashiko-bot@kernel.org
To: "Cheng Nie" <niecheng1@uniontech.com>
Cc: damon@lists.linux.dev
Subject: Re: [PATCH v2 2/2] selftests/damon/sysfs.py: validate memcg_path staging readback
Date: Fri, 29 May 2026 09:43:26 +0000 [thread overview]
Message-ID: <20260529094327.6D5031F00893@smtp.kernel.org> (raw)
In-Reply-To: <FF9A1552C03B7C88+20260529092131.1703337-1-niecheng1@uniontech.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The newly added `test_memcg_filter_memcg_path_staging` test inadvertently depends on `CONFIG_MEMCG` and active cgroup configurations due to a call to `commit()`, causing the test to fail inappropriately on environments lacking them.
--
commit 45ed1607d8ff8754a1a322fb6da3631cdc56f283
Author: Cheng Nie <niecheng1@uniontech.com>
selftests/damon/sysfs.py: validate memcg_path staging readback
This commit adds a dedicated test to selftests/damon/sysfs.py that writes
memcg_path to sysfs and verifies its readback. It aims to test the sysfs
behavior independently of the local userspace cgroup mount layout.
> diff --git a/tools/testing/selftests/damon/sysfs.py b/tools/testing/selftests/damon/sysfs.py
> index aa03a1187489f..0f20bc9c46b78 100755
> --- a/tools/testing/selftests/damon/sysfs.py
> +++ b/tools/testing/selftests/damon/sysfs.py
> @@ -250,6 +250,43 @@ def assert_ctxs_committed(kdamonds):
[ ... ]
> + context = _damon_sysfs.DamonCtx(
> + targets=[_damon_sysfs.DamonTarget(pid=-1)],
> + schemes=[_damon_sysfs.Damos(ops_filters=[memcg_filter])])
> + context.idx = 0
> + context.kdamond = kdamonds.kdamonds[0]
> + kdamonds.kdamonds[0].contexts = [context]
> +
> + err = kdamonds.kdamonds[0].commit()
[Severity: Medium]
Could this cause a regression where the test fails on environments lacking
memcg support or active cgroups?
The stated goal of this test is to validate the sysfs staging readback
without depending on local userspace cgroup mount layouts. However, when
commit() is called, it instructs the kernel to apply the configuration.
This triggers damon_sysfs_memcg_path_to_id(), which traverses online memory
cgroups and will return -EINVAL if memcg support is disabled or the root
cgroup '/' cannot be resolved to an active memcg. This causes the commit()
operation to fail, which makes the entire selftest report a regression.
Would it be better to only stage the values (e.g., via context.stage())
and then verify the readback, without triggering the operational commit
step?
> + if err is not None:
> + fail('memcg_path staging: kdamond commit', {'error': err})
--
Sashiko AI review · https://sashiko.dev/#/patchset/4CDA28DC581FDCF8+20260529090845.1696845-1-niecheng1@uniontech.com?part=2
next prev parent reply other threads:[~2026-05-29 9:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-29 9:08 [PATCH v2 0/2] selftests/damon: fix memcg_path staging handling Cheng Nie
2026-05-29 9:19 ` [PATCH v2 1/2] selftests/damon/_damon_sysfs.py: fix memcg_path assignment Cheng Nie
2026-05-29 14:52 ` SeongJae Park
2026-05-29 9:21 ` [PATCH v2 2/2] selftests/damon/sysfs.py: validate memcg_path staging readback Cheng Nie
2026-05-29 9:43 ` sashiko-bot [this message]
2026-05-29 15:03 ` SeongJae Park
2026-05-29 15:00 ` SeongJae Park
2026-06-01 0:53 ` Cheng Nie
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=20260529094327.6D5031F00893@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=damon@lists.linux.dev \
--cc=niecheng1@uniontech.com \
--cc=sashiko-reviews@lists.linux.dev \
/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.