mm/damon/tests/core-kunit: handle alloc failures on damon_test_merge_two()

commit 3d443dd29a1db7efa587a4bb0c06a497e13ca9e4 upstream.

damon_test_merge_two() is assuming all dynamic memory allocation in it
will succeed.  Those are indeed likely in the real use cases since those
allocations are too small to fail, but theoretically those could fail.  In
the case, inappropriate memory access can happen.  Fix it by appropriately
cleanup pre-allocated memory and skip the execution of the remaining tests
in the failure cases.

Link: https://lkml.kernel.org/r/20251101182021.74868-7-sj@kernel.org
Fixes: 17ccae8bb5c9 ("mm/damon: add kunit tests")
Signed-off-by: SeongJae Park <sj@kernel.org>
Cc: Brendan Higgins <brendan.higgins@linux.dev>
Cc: David Gow <davidgow@google.com>
Cc: Kefeng Wang <wangkefeng.wang@huawei.com>
Cc: <stable@vger.kernel.org>	[5.15+]
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

diff --git a/mm/damon/core-test.h b/mm/damon/core-test.h
index 02135cac70b3c495fb68408970e177b3633d9541..fc950fad0440f75992568ae1bafe756e807d8855 100644 (file)
--- a/mm/damon/core-test.h
+++ b/mm/damon/core-test.h
@@ -162,10 +162,20 @@ static void damon_test_merge_two(struct kunit *test)
        int i;
 
        t = damon_new_target();
+       if (!t)
+               kunit_skip(test, "target alloc fail");
        r = damon_new_region(0, 100);
+       if (!r) {
+               damon_free_target(t);
+               kunit_skip(test, "region alloc fail");
+       }
        r->nr_accesses = 10;
        damon_add_region(r, t);
        r2 = damon_new_region(100, 300);
+       if (!r2) {
+               damon_free_target(t);
+               kunit_skip(test, "second region alloc fail");
+       }
        r2->nr_accesses = 20;
        damon_add_region(r2, t);