From: SJ Park <sj@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Jason Angelov <jasonangelov@ucla.edu>,
Brendan Higgins <brendan.higgins@linux.dev>,
David Gow <davidgow@davidgow.net>, SJ Park <sj@kernel.org>,
damon@lists.linux.dev, kunit-dev@googlegroups.com,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-mm@kvack.org
Subject: [PATCH v2 2/2] mm/damon/core-kunit: test damon_valid_probe_params()
Date: Mon, 31 Aug 2026 08:06:49 -0700 [thread overview]
Message-ID: <20260831150650.84829-3-sj@kernel.org> (raw)
In-Reply-To: <20260831150650.84829-1-sj@kernel.org>
From: Jason Angelov <jasonangelov@ucla.edu>
damon_valid_probe_params() makes damon_commit_ctx() reject probe
configurations that could overflow a probe_hits counter, a single
(weight * probe_hits) product, or the sum of those products.
Add a kunit test covering each rejection at its boundary:
- samples per aggregation interval: U8_MAX is allowed, one more could
overflow a probe_hits counter
- single weight: the largest whose product fits in unsigned int is
allowed, one larger is rejected
- multiple probes: each product fits, but their sum overflows
- no weight set: the validation is skipped
Signed-off-by: Jason Angelov <jasonangelov@ucla.edu>
Reviewed-by: SJ Park <sj@kernel.org>
Signed-off-by: SJ Park <sj@kernel.org>
---
mm/damon/tests/core-kunit.h | 57 +++++++++++++++++++++++++++++++++++++
1 file changed, 57 insertions(+)
diff --git a/mm/damon/tests/core-kunit.h b/mm/damon/tests/core-kunit.h
index 68591ca99a4f7..af26b3d60957b 100644
--- a/mm/damon/tests/core-kunit.h
+++ b/mm/damon/tests/core-kunit.h
@@ -1341,6 +1341,62 @@ static void damon_test_commit_ctx(struct kunit *test)
damon_destroy_ctx(dst);
}
+static void damon_test_valid_probe_params(struct kunit *test)
+{
+ struct damon_ctx *ctx;
+ struct damon_probe *probe, *probe2;
+
+ ctx = damon_new_ctx();
+ if (!ctx)
+ kunit_skip(test, "ctx alloc fail");
+ probe = damon_new_probe();
+ if (!probe) {
+ damon_destroy_ctx(ctx);
+ kunit_skip(test, "probe alloc fail");
+ }
+ damon_add_probe(ctx, probe);
+
+ /* Parameters are validated only if any probe weight is set. */
+ ctx->attrs.sample_interval = 1;
+ ctx->attrs.aggr_interval = 1000000;
+ KUNIT_EXPECT_TRUE(test, damon_valid_probe_params(ctx));
+
+ /* Up to U8_MAX samples per aggregation interval are allowed. */
+ probe->weight = 100;
+ ctx->attrs.aggr_interval = 255;
+ KUNIT_EXPECT_TRUE(test, damon_valid_probe_params(ctx));
+
+ /* More samples could overflow the probe_hits counters. */
+ ctx->attrs.aggr_interval = 256;
+ KUNIT_EXPECT_FALSE(test, damon_valid_probe_params(ctx));
+
+ /* The largest weight whose weighted hit count fits in unsigned int. */
+ ctx->attrs.aggr_interval = 255;
+ probe->weight = UINT_MAX / 255;
+ KUNIT_EXPECT_TRUE(test, damon_valid_probe_params(ctx));
+
+ /* Any larger weight could overflow its weighted hit count. */
+ probe->weight = UINT_MAX / 255 + 1;
+ KUNIT_EXPECT_FALSE(test, damon_valid_probe_params(ctx));
+
+ /* With one sample per aggregation, even the largest weight fits. */
+ ctx->attrs.aggr_interval = 1;
+ probe->weight = UINT_MAX;
+ KUNIT_EXPECT_TRUE(test, damon_valid_probe_params(ctx));
+
+ /* The sum of all probes' weighted hit counts could also overflow. */
+ probe2 = damon_new_probe();
+ if (!probe2) {
+ damon_destroy_ctx(ctx);
+ kunit_skip(test, "probe2 alloc fail");
+ }
+ probe2->weight = 1;
+ damon_add_probe(ctx, probe2);
+ KUNIT_EXPECT_FALSE(test, damon_valid_probe_params(ctx));
+
+ damon_destroy_ctx(ctx);
+}
+
static void damos_test_filter_out(struct kunit *test)
{
struct damon_target *t;
@@ -1667,6 +1723,7 @@ static struct kunit_case damon_test_cases[] = {
KUNIT_CASE(damos_test_commit_migrate_hot),
KUNIT_CASE(damon_test_commit_target_regions),
KUNIT_CASE(damon_test_commit_ctx),
+ KUNIT_CASE(damon_test_valid_probe_params),
KUNIT_CASE(damos_test_filter_out),
KUNIT_CASE(damon_test_feed_loop_next_input),
KUNIT_CASE(damon_test_set_filters_default_reject),
--
2.47.3
next prev parent reply other threads:[~2026-08-31 15:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 15:06 [PATCH v2 0/2] mm/damon: add kunit tests for probe_hits handling and probe params validation SJ Park
2026-08-31 15:06 ` [PATCH v2 1/2] mm/damon/core-kunit: test probe_hits handling at region split and merge SJ Park
2026-08-31 18:10 ` sashiko-bot
2026-08-31 15:06 ` SJ Park [this message]
2026-08-31 18:15 ` [PATCH v2 2/2] mm/damon/core-kunit: test damon_valid_probe_params() sashiko-bot
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=20260831150650.84829-3-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=brendan.higgins@linux.dev \
--cc=damon@lists.linux.dev \
--cc=davidgow@davidgow.net \
--cc=jasonangelov@ucla.edu \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.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