From: SJ Park <sj@kernel.org>
To: SJ Park <sj@kernel.org>
Cc: stable@vger.kernel.org, damon@lists.linux.dev,
Brendan Higgins <brendan.higgins@linux.dev>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 6.1.y] mm/damon/core-kunit: check region count before testing in split_at()
Date: Tue, 8 Sep 2026 23:34:07 -0700 [thread overview]
Message-ID: <20260909063407.94616-1-sj@kernel.org> (raw)
In-Reply-To: <20260909035813.162131-1-sj@kernel.org>
On Tue, 8 Sep 2026 20:58:13 -0700 SJ Park <sj@kernel.org> wrote:
> damon_test_split_at() test next region that is assumed to be created by
> damon_split_region_at() invocation. But the split might fail. In this
> case, the succeeding test may dereference invalid pointers returned by
> damon_next_region().
>
> The invalid pointer may not cause a really bad user impact, because of the
> implementation detail. It would only read wrong contents in the belonging
> damon_target struct. Depending on the future change of the offset from
> the link header to the accessing field, this could also be really
> dangerous, though. Still, the realistic user impact would be limited. It
> would affect only test run setups.
>
> Fix it by testing if the number of regions was also changed as expected
> and exit early for the failure.
>
> The issue was discovered [1] by Sashiko.
>
> Link: https://lore.kernel.org/20260718001442.87129-3-sj@kernel.org
> Link: https://lore.kernel.org/20260714142352.100478-1-sj@kernel.org [1]
> Fixes: 17ccae8bb5c9 ("mm/damon: add kunit tests")
> Signed-off-by: SJ Park <sj@kernel.org>
> Cc: Brendan Higgins <brendan.higgins@linux.dev>
> Cc: <stable@vger.kernel.org> # 5.15.x
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> (cherry picked from commit 9b18ef3c3aa1ce24176e340061caf15fa2742564)
> Signed-off-by: SJ Park <sj@kernel.org>
> ---
> mm/damon/core-test.h | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/mm/damon/core-test.h b/mm/damon/core-test.h
> index d8fef225930a5..1dd17d43a642c 100644
> --- a/mm/damon/core-test.h
> +++ b/mm/damon/core-test.h
> @@ -162,6 +162,9 @@ static void damon_test_split_at(struct kunit *test)
> }
> damon_add_region(r, t);
> damon_split_region_at(t, r, 25);
> + KUNIT_EXPECT_EQ(test, damon_nr_regions(t), 2);
> + if (!damon_nr_regions(t) != 2)
> + goto out;
Sashiko found the above if condition has a typo. It should 's/!damon/damon/'.
Please ignore this patch. I will send a corrected patch as another reply.
> KUNIT_EXPECT_EQ(test, r->ar.start, 0ul);
> KUNIT_EXPECT_EQ(test, r->ar.end, 25ul);
>
> @@ -169,6 +172,7 @@ static void damon_test_split_at(struct kunit *test)
> KUNIT_EXPECT_EQ(test, r->ar.start, 25ul);
> KUNIT_EXPECT_EQ(test, r->ar.end, 100ul);
>
> +out:
> damon_free_target(t);
> damon_destroy_ctx(c);
> }
> --
> 2.47.3
>
>
Thanks,
SJ
next prev parent reply other threads:[~2026-09-09 6:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2026090820-envoy-endanger-c99b@gregkh>
2026-09-09 3:58 ` [PATCH 6.1.y] mm/damon/core-kunit: check region count before testing in split_at() SJ Park
2026-09-09 4:02 ` sashiko-bot
2026-09-09 6:32 ` SJ Park
2026-09-09 6:34 ` SJ Park [this message]
2026-09-09 6:36 ` SJ Park
2026-09-09 6:47 ` sashiko-bot
2026-09-09 20:26 ` Sasha Levin
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=20260909063407.94616-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=brendan.higgins@linux.dev \
--cc=damon@lists.linux.dev \
--cc=stable@vger.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.