From: SJ Park <sj@kernel.org>
To: Karl Mehltretter <kmehltretter@gmail.com>
Cc: SJ Park <sj@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Bijan Tabatabai <bijan311@gmail.com>,
damon@lists.linux.dev, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] mm/damon/core: preserve the quota passed to damon_new_scheme()
Date: Fri, 25 Sep 2026 01:47:12 -0700 [thread overview]
Message-ID: <20260925084713.46887-1-sj@kernel.org> (raw)
In-Reply-To: <20260924201615.4478-2-kmehltretter@gmail.com>
On Thu, 24 Sep 2026 22:16:13 +0200 Karl Mehltretter <kmehltretter@gmail.com> wrote:
> damon_commit_ctx() first commits the running context's parameters to a
> temporary context for validating proposed updates. When
> damon_commit_schemes() creates the temporary schemes, it passes the
> running scheme's quota as the quota parameter of damon_new_scheme().
>
> damon_new_scheme() calls damos_quota_init() on that quota before copying
> it to the new scheme. This clears the running scheme's effective quota,
> feedback input and charging state. Even an update rejected with -EINVAL
> loses the running quota state.
>
> For a size quota, this discards the bytes already charged and allows the
> scheme to use a fresh quota before the reset interval has elapsed. For a
> goal-driven quota, the consist tuner loses its accumulated input and
> restarts from its minimum input. A time quota loses its throughput
> estimate and falls back to the initial estimate.
The end users will show DAMOS works more or less aggressively than expected for
online-commit updates of quotas. DAMON provides best efforts by detault.
DAMON parameters online commit is supposed to be executed only occationally.
Hence, the issue wouldn't be critical on sane setups. For user_input type
quota goals, online commit of the user input score is expected to be frequent.
But, for the case commit_schemes_quota_goals command is recommended for optimal
execution, and it doesn't have this bug.
Karl, if you don't mind, I will add the above user impact detail to the commit
message when I apply this to damon/next.
>
> Commit 60bd24f272d0 ("mm/damon/sysfs: test commit input against realistic
> destination") introduced this problem in v6.19 when sysfs validation
> began committing the running context's parameters to a temporary context.
> Commit b90408ef1163 ("mm/damon/core: safely validate src on
> damon_commit_ctx()") later moved that validation into the core API,
> exposing other callers including DAMON_RECLAIM and DAMON_LRU_SORT.
>
> Sashiko reported the same side effect [1] on the RFC of the core API
> change.
>
> Copy the quota to the new scheme first, then initialize that copy. Make
> damos_quota_init() return void, since its return value is no longer needed.
Looks good to me. Thank you for finding and fixing this, Karl.
>
> Fixes: 60bd24f272d0 ("mm/damon/sysfs: test commit input against realistic destination")
> Cc: <stable@vger.kernel.org>
> Link: https://lore.kernel.org/r/20260702212143.0CB6D1F00A3D@smtp.kernel.org/ [1]
> Assisted-by: LLM
> Signed-off-by: Karl Mehltretter <kmehltretter@gmail.com>
Reviewed-by: SJ Park <sj@kernel.org>
Thanks,
SJ
[...]
next prev parent reply other threads:[~2026-09-25 8:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 20:16 [PATCH v2 0/2] mm/damon: preserve quota state when constructing schemes Karl Mehltretter
2026-09-24 20:16 ` [PATCH v2 1/2] mm/damon/core: preserve the quota passed to damon_new_scheme() Karl Mehltretter
2026-09-25 8:47 ` SJ Park [this message]
2026-09-24 20:16 ` [PATCH v2 2/2] mm/damon/tests/core-kunit: test preservation of quota state Karl Mehltretter
2026-09-25 8:52 ` [PATCH v2 0/2] mm/damon: preserve quota state when constructing schemes 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=20260925084713.46887-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bijan311@gmail.com \
--cc=damon@lists.linux.dev \
--cc=kmehltretter@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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®