From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: SeongJae Park <sj@kernel.org>, <akpm@linux-foundation.org>
Cc: <damon@lists.linux.dev>, <linux-mm@kvack.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm/damon/core-test: add a test for damon_set_attrs()
Date: Fri, 16 Jun 2023 09:48:30 +0800 [thread overview]
Message-ID: <f0aa8017-9136-0c77-291c-0db5c3c6fde3@huawei.com> (raw)
In-Reply-To: <20230615183323.87561-1-sj@kernel.org>
On 2023/6/16 2:33, SeongJae Park wrote:
> Commit 5ff6e2fff88e ("mm/damon/core: fix divide error in
> damon_nr_accesses_to_accesses_bp()") fixed a bug by adding arguments
> validation in damon_set_attrs(). Add a unit test for the added
> validation to ensure the bug cannot occur again.
>
> Signed-off-by: SeongJae Park <sj@kernel.org>
Reviewed-by: Kefeng Wang <wangkefeng.wang@huawei.com>
> ---
> mm/damon/core-test.h | 24 ++++++++++++++++++++++++
> 1 file changed, 24 insertions(+)
>
> diff --git a/mm/damon/core-test.h b/mm/damon/core-test.h
> index fae64d32b925..c11210124344 100644
> --- a/mm/damon/core-test.h
> +++ b/mm/damon/core-test.h
> @@ -318,6 +318,29 @@ static void damon_test_update_monitoring_result(struct kunit *test)
> KUNIT_EXPECT_EQ(test, r->age, 20);
> }
>
> +static void damon_test_set_attrs(struct kunit *test)
> +{
> + struct damon_ctx ctx;
> + struct damon_attrs valid_attrs = {
> + .min_nr_regions = 10, .max_nr_regions = 1000,
> + .sample_interval = 5000, .aggr_interval = 100000,};
> + struct damon_attrs invalid_attrs;
> +
> + KUNIT_EXPECT_EQ(test, damon_set_attrs(&ctx, &valid_attrs), 0);
> +
> + invalid_attrs = valid_attrs;
> + invalid_attrs.min_nr_regions = 1;
> + KUNIT_EXPECT_EQ(test, damon_set_attrs(&ctx, &invalid_attrs), -EINVAL);
> +
> + invalid_attrs = valid_attrs;
> + invalid_attrs.max_nr_regions = 9;
> + KUNIT_EXPECT_EQ(test, damon_set_attrs(&ctx, &invalid_attrs), -EINVAL);
> +
> + invalid_attrs = valid_attrs;
> + invalid_attrs.aggr_interval = 4999;
> + KUNIT_EXPECT_EQ(test, damon_set_attrs(&ctx, &invalid_attrs), -EINVAL);
> +}
> +
> static struct kunit_case damon_test_cases[] = {
> KUNIT_CASE(damon_test_target),
> KUNIT_CASE(damon_test_regions),
> @@ -329,6 +352,7 @@ static struct kunit_case damon_test_cases[] = {
> KUNIT_CASE(damon_test_ops_registration),
> KUNIT_CASE(damon_test_set_regions),
> KUNIT_CASE(damon_test_update_monitoring_result),
> + KUNIT_CASE(damon_test_set_attrs),
> {},
> };
>
prev parent reply other threads:[~2023-06-16 1:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 18:33 SeongJae Park
2023-06-16 1:48 ` Kefeng Wang [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=f0aa8017-9136-0c77-291c-0db5c3c6fde3@huawei.com \
--to=wangkefeng.wang@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=damon@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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