From: sashiko-bot@kernel.org
To: "SJ Park" <sj@kernel.org>
Cc: damon@lists.linux.dev
Subject: Re: [RFC PATCH v1.1 08/10] selftests/damon/sysfs.sh: test hugepage_mem_bp quota goal
Date: Wed, 29 Jul 2026 03:45:05 +0000 [thread overview]
Message-ID: <20260729034505.933E51F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260729033751.131213-9-sj@kernel.org>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The selftest script expects the kernel to accept the 'hugepage_mem_bp' metric for the DAMON sysfs quota goal, but the corresponding kernel feature implementation is missing from this patch series. Writing this value to the `target_metric` sysfs file will return `-EINVAL`, causing the test to unconditionally fail and exit.
--
--- Patch [8]: [RFC PATCH v1.1 08/10] selftests/damon/sysfs.sh: test hugepage_mem_bp quota goal ---
commit 6c11ff9f30e87caf7ac58e12f507a641d985aebc
Author: SJ Park <sj@kernel.org>
selftests/damon/sysfs.sh: test hugepage_mem_bp quota goal
This commit updates the DAMON sysfs selftest to verify that the quota goal
target_metric file accepts the new hugepage_mem_bp input.
> diff --git a/tools/testing/selftests/damon/sysfs.sh b/tools/testing/selftests/damon/sysfs.sh
> index f7fb94b84e716..8690aef1e436c 100755
> --- a/tools/testing/selftests/damon/sysfs.sh
> +++ b/tools/testing/selftests/damon/sysfs.sh
> @@ -210,6 +210,7 @@ test_goal()
> ensure_write_succ "$fpath" "active_mem_bp" "valid input"
> ensure_write_succ "$fpath" "inactive_mem_bp" "valid input"
> ensure_write_succ "$fpath" "node_eligible_mem_bp" "valid input"
> + ensure_write_succ "$fpath" "hugepage_mem_bp" "valid input"
[Severity: Medium]
Will this test reliably fail because the kernel implementation for the
hugepage_mem_bp metric is missing from this patch series?
If the corresponding kernel feature isn't included, writing this value
to the target_metric sysfs file in test_goal() will return -EINVAL. This
would cause ensure_write_succ() to unconditionally fail and abort the
selftest.
> ensure_write_fail "$fpath" "foo" "invalid input"
> ensure_file "$goal_dir/nid" "exist" "600"
> ensure_file "$goal_dir/path" "exist" "600"
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260729033751.131213-1-sj@kernel.org?part=8
next prev parent reply other threads:[~2026-07-29 3:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 3:37 [RFC PATCH v1.1 00/10] mm/damon: cleanup code, add test cases, and update guidances in docs SJ Park
2026-07-29 3:37 ` [RFC PATCH v1.1 01/10] mm/damon/core: use damon_nr_samples_per_aggr() for max merge threshold SJ Park
2026-07-29 3:37 ` [RFC PATCH v1.1 02/10] mm/damon/core: remove debug messages SJ Park
2026-07-29 3:37 ` [RFC PATCH v1.1 03/10] mm/damon/vaddr: remove a debug message SJ Park
2026-07-29 3:37 ` [RFC PATCH v1.1 04/10] mm/damon/tests/core-kunit: extend set_regions() test for error case SJ Park
2026-07-29 3:37 ` [RFC PATCH v1.1 05/10] mm/damon/tests/core-kunit: test <=0 size damon_set_regions() inputs SJ Park
2026-07-29 3:37 ` [RFC PATCH v1.1 06/10] mm/damon/tests/core-kunit: test overlapping ranges for set_regions() SJ Park
2026-07-29 3:48 ` sashiko-bot
2026-07-29 3:56 ` SJ Park
2026-07-29 3:37 ` [RFC PATCH v1.1 07/10] mm/damon/tests/core-kunit: test damon_nr_samples_per_aggr() SJ Park
2026-07-29 3:37 ` [RFC PATCH v1.1 08/10] selftests/damon/sysfs.sh: test hugepage_mem_bp quota goal SJ Park
2026-07-29 3:45 ` sashiko-bot [this message]
2026-07-29 3:57 ` SJ Park
2026-07-29 3:37 ` [RFC PATCH v1.1 09/10] Docs/mm/damon/maintainer-profile: update AI review for Sashiko replies SJ Park
2026-07-29 3:37 ` [RFC PATCH v1.1 10/10] Docs/ABI/damon: recommend subsystem doc instead of admin-guide 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=20260729034505.933E51F000E9@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 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.