From: sashiko-bot@kernel.org
To: "SJ Park" <sj@kernel.org>
Cc: damon@lists.linux.dev
Subject: Re: [RFC PATCH 1/7] mm/damon/core: introduce damos_quota_goal->complement
Date: Fri, 18 Sep 2026 14:48:17 +0000 [thread overview]
Message-ID: <20260918144818.18C831F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260918142827.85303-2-sj@kernel.org>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] mm: integer underflow in damos_set_quota_goal_current_value() for complemented metrics
--
commit 94b0fa41235165f1d082ca5735dcefbf9f65199b
Author: SJ Park <sj@kernel.org>
mm/damon/core: introduce damos_quota_goal->complement
This commit introduces the complement field to struct damos_quota_goal
to allow specifying whether to use a complemented value of the goal target
metric. It adds the field and implements the core support, handling the flag
during quota goal commit and current quota goal metric value retrieval.
> diff --git a/mm/damon/core.c b/mm/damon/core.c
> index 2258b72da7a78..25a8221dd2a40 100644
> --- a/mm/damon/core.c
> +++ b/mm/damon/core.c
[ ... ]
> @@ -3238,6 +3239,19 @@ static void damos_set_quota_goal_current_value(struct damon_ctx *c,
> default:
> break;
> }
> + if (!goal->complement)
> + return;
> +
> + /* updte current_value to complemented value */
> +
> + /* for user_input, users set complemented value on their own */
> + if (goal->metric == DAMOS_QUOTA_USER_INPUT)
> + return;
> + if (goal->metric == DAMOS_QUOTA_SOME_MEM_PSI_US)
> + goal->current_value = s->quota.reset_interval * 1000 -
> + goal->current_value;
> + else
> + goal->current_value = 10000 - goal->current_value;
[Severity: High]
Can this unsigned subtraction result in an integer underflow?
In damos_set_quota_goal_current_value(), if the measured memory stall
(current_value) exceeds the reset interval due to kdamond thread
scheduling delays, heavy system load, or if the user configures
reset_interval_ms to 0 via sysfs, s->quota.reset_interval * 1000 -
goal->current_value will underflow.
Similarly, for BP metrics relying on loosely-coupled lockless kernel counters
(e.g., global_node_page_state), per-CPU drift can occasionally cause the
returned value to exceed 10000, causing 10000 - goal->current_value to
underflow.
If an underflow occurs, it produces a value near ULONG_MAX.
Would passing this immense value to the auto-tuner mistakenly drop the scheme's
reclaim quota to its minimum precisely when memory pressure is highest?
> }
>
> /* Return the highest score since it makes schemes least aggressive */
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260918142827.85303-1-sj@kernel.org?part=1
next prev parent reply other threads:[~2026-09-18 14:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 14:28 [RFC PATCH 0/7] mm/damon: introduce damos quota goal target metric complement flag SJ Park
2026-09-18 14:28 ` [RFC PATCH 1/7] mm/damon/core: introduce damos_quota_goal->complement SJ Park
2026-09-18 14:48 ` sashiko-bot [this message]
2026-09-18 15:08 ` SJ Park
2026-09-18 14:28 ` [RFC PATCH 2/7] mm/damon: add complement argument to damos_new_quota_goal() SJ Park
2026-09-18 14:56 ` sashiko-bot
2026-09-18 14:28 ` [RFC PATCH 3/7] mm/damon/sysfs-schemes: support quota goal complement flag SJ Park
2026-09-18 15:05 ` sashiko-bot
2026-09-18 15:09 ` SJ Park
2026-09-18 14:28 ` [RFC PATCH 4/7] mm/damon/tests/core-kunit: test quota_goal->complement commit SJ Park
2026-09-18 15:07 ` sashiko-bot
2026-09-18 14:28 ` [RFC PATCH 5/7] Docs/mm/damon/design: document damos quota goal complement flag SJ Park
2026-09-18 15:07 ` sashiko-bot
2026-09-18 14:28 ` [RFC PATCH 6/7] Docs/admin-guide/mm/damon/usage: update for quota goal complement file SJ Park
2026-09-18 15:09 ` sashiko-bot
2026-09-18 15:11 ` SJ Park
2026-09-18 14:28 ` [RFC PATCH 7/7] Docs/ABI/damon: update for quota goal metric complement sysfs file SJ Park
2026-09-18 15:21 ` sashiko-bot
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=20260918144818.18C831F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=damon@lists.linux.dev \
--cc=sashiko-reviews@lists.linux.dev \
--cc=sj@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