FAILED: patch "[PATCH] mm/damon/vaddr-kunit: check region count in three_regions" failed to apply to 6.12-stable tree
Subsystems (3)
[email protected]
maintainerThe patch below does not apply to the 6.12-stable tree.
If someone wants it applied there, or to any other stable or longterm tree, then please email the backport, including the original git commit id to <[email protected]>.
To reproduce the conflict and resubmit, you may use the following commands:
git fetch https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/ linux-6.12.y
git checkout FETCH_HEAD
git cherry-pick -x 5fea07e460874c8c7cf00f728efbe22abc62c8d8
# <resolve conflicts, build, test, etc.>
git commit -s
git send-email --to '<[email protected]>' --in-reply-to '2026090819-haiku-machinist-83fa@gregkh' --subject-prefix 'PATCH 6.12.y' 'HEAD^..'
Possible dependencies:
thanks,
greg k-h
------------------ original commit in Linus's tree ------------------
From 5fea07e460874c8c7cf00f728efbe22abc62c8d8 Mon Sep 17 00:00:00 2001
From: SJ Park <[email protected]>
Date: Fri, 17 Jul 2026 17:14:37 -0700
Subject: [PATCH] mm/damon/vaddr-kunit: check region count in three_regions
test
damon_do_test_apply_three_regions() iterates regions after damon_set_regions() call assuming the function would succeed at setting the number of regions the same to the expected one. It might have failed. In this case, __nth_region_of() in the iteration could return NULL and NULL dereference can happen in the test.
The consequent user impact (NULL dereference) is quite bad. The realistic user impact would be limited, though. 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.
mm/damon/tests/vaddr-kunit.h +5 -0
@@ -158,12 +158,17 @@ static void damon_do_test_apply_three_regions(struct kunit *test,kunit_skip (test,"second damon_set_regions() fail" ); } +KUNIT_EXPECT_EQ (test,damon_nr_regions (t), nr_expected /2 ); +if (damon_nr_regions (t) != nr_expected /2 ) + goto out; +for (i =0 ; i < nr_expected /2 ; i++) { r =__nth_region_of (t, i);KUNIT_EXPECT_EQ (test, r->ar.start, expected[i *2 ]);KUNIT_EXPECT_EQ (test, r->ar.end, expected[i *2 +1 ]); } +out:damon_destroy_target (t,NULL ); }
SJ Park
maintainerPATCH 1/1 mm/damon/vaddr-kunit: check region count in three_regions test
damon_do_test_apply_three_regions() iterates regions after damon_set_regions() call assuming the function would succeed at setting the number of regions the same to the expected one. It might have failed. In this case, __nth_region_of() in the iteration could return NULL and NULL dereference can happen in the test.
The consequent user impact (NULL dereference) is quite bad. The realistic user impact would be limited, though. 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.
--- mm/damon/tests/vaddr-kunit.h | 5 +++++ 1 file changed, 5 insertions(+)
mm/damon/tests/vaddr-kunit.h +5 -0
@@ -149,12 +149,17 @@ static void damon_do_test_apply_three_regions(struct kunit *test,damon_set_regions (t, three_regions,3 ); +KUNIT_EXPECT_EQ (test,damon_nr_regions (t), nr_expected /2 ); +if (damon_nr_regions (t) != nr_expected /2 ) + goto out; +for (i =0 ; i < nr_expected /2 ; i++) { r =__nth_region_of (t, i);KUNIT_EXPECT_EQ (test, r->ar.start, expected[i *2 ]);KUNIT_EXPECT_EQ (test, r->ar.end, expected[i *2 +1 ]); } +out:damon_destroy_target (t); }
Signature · 1 line
2.47.3
[email protected]
AI reviewRe: [PATCH 6.12.y] mm/damon/vaddr-kunit: check region count in three_regions test
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
Pre-existing issues:
- [High] Incomplete fix: The same vulnerable test pattern fixed by this patch in vaddr-kunit.h also exists in mm/damon/tests/core-kunit.h within damon_test_merge_regions_of(), where a hardcoded loop accesses regions via __nth_region_of() after an unchecked operation. --
commit 95900378d75f76847738ad9f2040d727e3455432
Author: SJ Park <[email protected]>
mm/damon/vaddr-kunit: check region count in three_regions test
This commit adds a check in damon_do_test_apply_three_regions() to verify that damon_set_regions() updated the region count as expected. If the count is wrong, it exits early to prevent a potential NULL pointer dereference when accessing the regions.
Quoted 7 lines
mm/damon/tests/vaddr-kunit.h +0
-0@@ -149,12 +149,17 @@ static void damon_do_test_apply_three_regions(struct kunit *test,damon_set_regions (t, three_regions,3 );
mm/damon/tests/vaddr-kunit.h static void damon_do_test_apply_three_regions(struct kunit *test, · line 160
Quoted 10 lines
mm/damon/tests/vaddr-kunit.h +4
-0+KUNIT_EXPECT_EQ (test,damon_nr_regions (t), nr_expected /2 ); +if (damon_nr_regions (t) != nr_expected /2 ) + goto out; +for (i =0 ; i < nr_expected /2 ; i++) { r =__nth_region_of (t, i);KUNIT_EXPECT_EQ (test, r->ar.start, expected[i *2 ]);KUNIT_EXPECT_EQ (test, r->ar.end, expected[i *2 +1 ]); }
[Severity: High]
This is a pre-existing issue, but should a similar fix also be applied to mm/damon/tests/core-kunit.h?
Looking at damon_test_merge_regions_of() in mm/damon/tests/core-kunit.h, there is an identical vulnerable pattern:
KUNIT_EXPECT_EQ(test, damon_nr_regions(t), 5u);
for (i = 0; i < 5; i++) {
r = __nth_region_of(t, i);
KUNIT_EXPECT_EQ(test, r->ar.start, saddrs[i]);If a regression causes damon_merge_regions_of() to return fewer than 5 regions, the KUNIT_EXPECT_EQ() check will log a failure but will not abort execution.
Will the subsequent loop continue executing past the actual number of regions, causing __nth_region_of(t, i) to return NULL? Does this result in a NULL pointer dereference when accessing r->ar.start that crashes the test execution environment?
Signature · 1 line
Sashiko AI review · https://sashiko.dev/#/patchset/[email protected]?part=1
Re: [PATCH 6.12.y] mm/damon/vaddr-kunit: check region count in three_regions test
In reply to SJ ParkQuoted 3 lines
damon_do_test_apply_three_regions()iterates regions afterdamon_set_regions()call assuming the function would succeed at setting the number of regions the same to the expected one. It might have failed.
Queued for 6.12, thanks.
Signature · 2 lines
Thanks, Sasha