From: sashiko-bot@kernel.org
To: "SJ Park" <sj@kernel.org>
Cc: damon@lists.linux.dev
Subject: Re: [RFC PATCH v2 8/8] mm/damon/core-kunit: test invalid damos filter commits
Date: Sun, 13 Sep 2026 17:28:01 +0000 [thread overview]
Message-ID: <20260913172801.C0B131F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260913171706.103052-9-sj@kernel.org>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Incomplete implementation: missing test coverage for DAMOS_FILTER_TYPE_PROBE_HITS_WSUM invalid commits.
--
commit d95c459dddaa5a1cc3be54d53b10942b9bd9ba9f
Author: SJ Park <sj@kernel.org>
mm/damon/core-kunit: test invalid damos filter commits
This commit adds KUnit test cases to verify the validation of damos filter
arguments at commit time.
> diff --git a/mm/damon/tests/core-kunit.h b/mm/damon/tests/core-kunit.h
> index 2b0931cf6fb32..527abc2570616 100644
> --- a/mm/damon/tests/core-kunit.h
> +++ b/mm/damon/tests/core-kunit.h
> @@ -1184,6 +1184,13 @@ static void damos_test_commit_filter(struct kunit *test)
> .allow = false,
> .sz_range = {.min = 234, .max = 345},
> }, false);
> + damos_test_commit_filter_for(test, &dst,
> + &(struct damos_filter){
> + .type = DAMOS_FILTER_TYPE_HUGEPAGE_SIZE,
> + .matching = false,
> + .allow = false,
> + .sz_range = {.min = 456, .max = 123},
> + }, true);
> damos_test_commit_filter_for(test, &dst,
> &(struct damos_filter){
> .type = DAMOS_FILTER_TYPE_UNMAPPED,
> @@ -1197,6 +1204,13 @@ static void damos_test_commit_filter(struct kunit *test)
> .allow = false,
> .addr_range = {.start = 456, .end = 567},
> }, false);
> + damos_test_commit_filter_for(test, &dst,
> + &(struct damos_filter){
> + .type = DAMOS_FILTER_TYPE_ADDR,
> + .matching = false,
> + .allow = false,
> + .addr_range = {.start = 567, .end = 456},
> + }, true);
[Severity: Medium]
Is a test case for DAMOS_FILTER_TYPE_PROBE_HITS_WSUM missing here?
Previous changes introduced range validation (max < min) for ADDR,
HUGEPAGE_SIZE, and PROBE_HITS_WSUM. While ADDR and HUGEPAGE_SIZE are being
tested for invalid commits, PROBE_HITS_WSUM seems to be omitted.
Additionally, if a test for PROBE_HITS_WSUM is added, does
damos_test_commit_filter_for() also need an update? The switch statement
verifying copied filter fields lacks a case for it and would fall through to
default, failing to verify the range arguments:
damos_test_commit_filter_for() {
...
switch (src->type) {
case DAMOS_FILTER_TYPE_MEMCG:
...
case DAMOS_FILTER_TYPE_HUGEPAGE_SIZE:
...
default:
break;
}
}
> damos_test_commit_filter_for(test, &dst,
> &(struct damos_filter){
> .type = DAMOS_FILTER_TYPE_TARGET,
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260913171706.103052-1-sj@kernel.org?part=8
next prev parent reply other threads:[~2026-09-13 17:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-13 17:16 [RFC PATCH v2 0/8] mm/damon: move damos filter range arguments validation to core SJ Park
2026-09-13 17:16 ` [RFC PATCH v2 1/8] mm/damon/sysfs-schemes: read sysfs_filter->addr_range only once SJ Park
2026-09-13 17:32 ` sashiko-bot
2026-09-13 17:16 ` [RFC PATCH v2 2/8] mm/damon/sysfs-schemes: read sysfs_filter->sz_range " SJ Park
2026-09-13 17:29 ` sashiko-bot
2026-09-13 17:17 ` [RFC PATCH v2 3/8] mm/damon/core: return an error from damos_commit_filter_arg() SJ Park
2026-09-13 17:25 ` sashiko-bot
2026-09-13 17:17 ` [RFC PATCH v2 4/8] mm/damon/core: disallow max < min damos filter range arguments commit SJ Park
2026-09-13 17:26 ` sashiko-bot
2026-09-13 17:17 ` [RFC PATCH v2 5/8] mm/damon/sysfs-schemes: drop centralized filter range arg validations SJ Park
2026-09-13 17:25 ` sashiko-bot
2026-09-13 17:17 ` [RFC PATCH v2 6/8] mm/damon/sysfs-schemes: use switch-case in add_scheme_filters() SJ Park
2026-09-13 17:22 ` sashiko-bot
2026-09-13 17:17 ` [RFC PATCH v2 7/8] mm/damon/core-kunit: extend damos_commit_filter_for() for wrong input SJ Park
2026-09-13 17:22 ` sashiko-bot
2026-09-13 17:17 ` [RFC PATCH v2 8/8] mm/damon/core-kunit: test invalid damos filter commits SJ Park
2026-09-13 17:28 ` sashiko-bot [this message]
2026-09-13 17:50 ` 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=20260913172801.C0B131F000FF@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox