[merged mm-stable] mm-damon-sysfs-do-not-directly-access-damon_ctx-ops.patch removed from -mm tree

[merged mm-stable] mm-damon-sysfs-do-not-directly-access-damon_ctx-ops.patch removed from -mm tree

[Andrew Morton]

The quilt patch titled
     Subject: mm/damon/sysfs: do not directly access damon_ctx->ops
has been removed from the -mm tree.  Its filename was
     mm-damon-sysfs-do-not-directly-access-damon_ctx-ops.patch

This patch was dropped because it was merged into the mm-stable branch
of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm

------------------------------------------------------
From: SJ Park <sj@kernel.org>
Subject: mm/damon/sysfs: do not directly access damon_ctx->ops
Date: Tue, 14 Jul 2026 07:35:42 -0700

damon_ctx->ops field is intended to be used by only the DAMON core layer. 
DAMON_SYSFS is directly reading the field to find if it is for physical
address monitoring, though.  Use the API function for the purpose,
damon_target_has_pid(), instead.

Link: https://lore.kernel.org/20260714143544.101305-10-sj@kernel.org
Signed-off-by: SJ Park <sj@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---

 mm/damon/sysfs.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

--- a/mm/damon/sysfs.c~mm-damon-sysfs-do-not-directly-access-damon_ctx-ops
+++ a/mm/damon/sysfs.c
@@ -2051,7 +2051,7 @@ static int damon_sysfs_add_targets(struc
 	int i, err;
 
 	/* Multiple physical address space monitoring targets makes no sense */
-	if (ctx->ops.id == DAMON_OPS_PADDR && sysfs_targets->nr > 1)
+	if (!damon_target_has_pid(ctx) && sysfs_targets->nr > 1)
 		return -EINVAL;
 
 	for (i = 0; i < sysfs_targets->nr; i++) {
_

Patches currently in -mm which might be from sj@kernel.org are