From: Andrew Morton <akpm@linux-foundation.org>
To: SeongJae Park <sj@kernel.org>
Cc: "# 6 . 15 . x" <stable@vger.kernel.org>,
damon@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH] mm/damon/core: avoid use of half-online-committed context
Date: Thu, 19 Mar 2026 19:48:49 -0700 [thread overview]
Message-ID: <20260319194849.64b0911e2a7a6d8b1c22005a@linux-foundation.org> (raw)
In-Reply-To: <20260319145218.86197-1-sj@kernel.org>
On Thu, 19 Mar 2026 07:52:17 -0700 SeongJae Park <sj@kernel.org> wrote:
> One major usage of damon_call() is online DAMON parameters update. It
> is done by calling damon_commit_ctx() inside the damon_call() callback
> function. damon_commit_ctx() can fail for two reasons: 1) invalid
> parameters and 2) internal memory allocation failures. In case of
> failures, the damon_ctx that attempted to be updated (commit
> destination) can be partially updated (or, corrupted from a
> perspective), and therefore shouldn't be used anymore. The function
> only ensures the damon_ctx object can safely deallocated using
> damon_destroy_ctx().
>
> The API callers are, however, calling damon_commit_ctx() only after
> asserting the parameters are valid, to avoid damon_commit_ctx() fails
> due to invalid input parameters. But it can still theoretically fail if
> the internal memory allocation fails. In the case, DAMON may run with
> the partially updated damon_ctx. This can result in unexpected
> behaviors including even NULL pointer dereference in case of
> damos_commit_dests() failure [1]. Such allocation failure is arguably
> too small to fail, so the real world impact would be rare. But, given
> the bad consequence, this needs to be fixed.
>
> Avoid such partially-committed (maybe-corrupted) damon_ctx use by saving
> the damon_commit_ctx() failure on the damon_ctx object. For this,
> introduce damon_ctx->maybe_corrupted field. damon_commit_ctx() sets it
> when it is failed. kdamond_call() checks if the field is set after each
> damon_call_control->fn() is executed. If it is set, ignore remaining
> callback requests and return. All kdamond_call() callers including
> kdamond_fn() also check the maybe_corrupted field right after
> kdamond_call() invocations. If the field is set, break the
> kdamond_fn() main loop so that DAMON sill doesn't use the context that
> might be corrupted.
I guess you saw the AI review?
https://sashiko.dev/#/patchset/20260319145218.86197-1-sj%40kernel.org
next prev parent reply other threads:[~2026-03-20 2:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 14:52 SeongJae Park
2026-03-20 2:48 ` Andrew Morton [this message]
2026-03-20 3:15 ` SeongJae Park
2026-03-21 2:16 ` SeongJae Park
2026-03-21 2:25 ` SeongJae Park
2026-03-22 19:26 ` SeongJae Park
2026-03-22 19:32 ` SeongJae 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=20260319194849.64b0911e2a7a6d8b1c22005a@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=damon@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=sj@kernel.org \
--cc=stable@vger.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