From: "Xiaolei Wang (Kaihong)" <xiaoleiwangxiaolei@gmail.com>
To: sj@kernel.org, akpm@linux-foundation.org, david@kernel.org,
ljs@kernel.org, error27@gmail.com, xiaoleiwangxiaolei@gmail.com
Cc: damon@lists.linux.dev, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
"Liam R. Howlett" <liam@infradead.org>,
Michal Hocko <mhocko@suse.com>, Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Vlastimil Babka <vbabka@kernel.org>
Subject: [PATCH] mm/damon/core: reject empty access pattern intervals on scheme commit
Date: Tue, 3 Nov 2026 18:54:18 +0800 [thread overview]
Message-ID: <20261103105418.362459-1-xiaoleiwangxiaolei@gmail.com> (raw)
DAMOS schemes accept access pattern bounds with min > max (e.g.
min_sz_region > max_sz_region). No input path validates the bounds:
damon_new_scheme() stores the pattern as is, and the sysfs ul_range
stores are plain kstrtoul().
At runtime __damos_valid_target() evaluates "min <= x <= max" for each
of the three pattern dimensions. A reversed interval is an empty set,
so every region fails the check and the scheme silently never matches
anything: nr_tried stays zero forever while the kdamond keeps running
normally.
With such a reversed interval, damo starts normally (rc=0, kdamond
state=on), but nr_tried and nr_applied stay zero forever and the target
RSS does not drop.
The same holds for the watermarks thresholds, which must be monotonic
(low <= mid <= high).
Validate the access pattern and watermarks at the beginning of
damos_commit(), through which both new schemes (damo start) and online
updates (damo tune) pass.
Fixes: 1f366e421c8f ("mm/damon/core: implement DAMON-based Operation Schemes (DAMOS)")
Cc: stable@vger.kernel.org
Cc: Liam R. Howlett <liam@infradead.org>
Cc: Michal Hocko <mhocko@suse.com>
Cc: Mike Rapoport <rppt@kernel.org>
Cc: Suren Baghdasaryan <surenb@google.com>
Cc: Vlastimil Babka <vbabka@kernel.org>
Signed-off-by: Xiaolei Wang (Kaihong) <xiaoleiwangxiaolei@gmail.com>
---
mm/damon/core.c | 19 +++++++++++++++++++
1 file changed, 19 insertions(+)
diff --git a/mm/damon/core.c b/mm/damon/core.c
index eb1fcdabc007..865627bda240 100644
--- a/mm/damon/core.c
+++ b/mm/damon/core.c
@@ -1566,10 +1566,29 @@ static struct damos *damon_nth_scheme(int n, struct damon_ctx *ctx)
return NULL;
}
+static int damos_validate_scheme(struct damos *s)
+{
+ struct damos_access_pattern *p = &s->pattern;
+ struct damos_watermarks *wmarks = &s->wmarks;
+
+ if (p->min_sz_region > p->max_sz_region ||
+ p->min_nr_accesses > p->max_nr_accesses ||
+ p->min_age_region > p->max_age_region)
+ return -EINVAL;
+ if (wmarks->metric != DAMOS_WMARK_NONE &&
+ (wmarks->low > wmarks->mid || wmarks->mid > wmarks->high))
+ return -EINVAL;
+ return 0;
+}
+
static int damos_commit(struct damos *dst, struct damos *src)
{
int err;
+ err = damos_validate_scheme(src);
+ if (err)
+ return err;
+
dst->pattern = src->pattern;
dst->action = src->action;
dst->apply_interval_us = src->apply_interval_us;
--
2.53.0
next reply other threads:[~2026-11-03 11:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 10:54 Xiaolei Wang (Kaihong) [this message]
2026-11-03 11:44 ` Aveline Noir
2026-11-03 14:53 ` SJ Park
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=20261103105418.362459-1-xiaoleiwangxiaolei@gmail.com \
--to=xiaoleiwangxiaolei@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=damon@lists.linux.dev \
--cc=david@kernel.org \
--cc=error27@gmail.com \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=rppt@kernel.org \
--cc=sj@kernel.org \
--cc=stable@vger.kernel.org \
--cc=surenb@google.com \
--cc=vbabka@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
all inboxes | Powered by JetHome®