From: SJ Park <sj@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: SJ Park <sj@kernel.org>,
damon@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: [PATCH 09/11] mm/damon/core: wait ctx stop in damon_call() before reruning an error
Date: Mon, 6 Jul 2026 07:06:24 -0700 [thread overview]
Message-ID: <20260706140628.87414-10-sj@kernel.org> (raw)
In-Reply-To: <20260706140628.87414-1-sj@kernel.org>
damon_call() failure means the DAMON context started its termination.
The termination is asynchronously done in kdamond thread. The caller's
error handling should handle the race, too. It is complicated and easy
to make mistakes.
Update damon_call() to ensure the context is stopped in the case, by
waiting until the completion is confirmed.
Signed-off-by: SJ Park <sj@kernel.org>
---
mm/damon/core.c | 12 ++++++++++--
1 file changed, 10 insertions(+), 2 deletions(-)
diff --git a/mm/damon/core.c b/mm/damon/core.c
index 08510bf9b38da..390e00b3685ef 100644
--- a/mm/damon/core.c
+++ b/mm/damon/core.c
@@ -2010,6 +2010,8 @@ int damon_kdamond_pid(struct damon_ctx *ctx)
* @ctx has succeeded. Otherwise, this function could fall into an indefinite
* wait.
*
+ * When this function is failed, the @ctx is guaranteed to be stopped.
+ *
* Return: 0 on success, negative error code otherwise.
*/
int damon_call(struct damon_ctx *ctx, struct damon_call_control *control)
@@ -2022,7 +2024,7 @@ int damon_call(struct damon_ctx *ctx, struct damon_call_control *control)
mutex_lock(&ctx->call_controls_lock);
if (ctx->call_controls_obsolete) {
mutex_unlock(&ctx->call_controls_lock);
- return -ECANCELED;
+ goto canceled;
}
list_add_tail(&control->list, &ctx->call_controls);
mutex_unlock(&ctx->call_controls_lock);
@@ -2030,8 +2032,14 @@ int damon_call(struct damon_ctx *ctx, struct damon_call_control *control)
return 0;
wait_for_completion(&control->completion);
if (control->canceled)
- return -ECANCELED;
+ goto canceled;
return 0;
+
+canceled:
+ while (damon_is_running(ctx))
+ schedule_timeout_idle(msecs_to_jiffies(100));
+ return -ECANCELED;
+
}
/**
--
2.47.3
next prev parent reply other threads:[~2026-07-06 14:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-06 14:06 [PATCH 00/11] mm/damon: refactor damon_{start,stop,commit}() for simple error handling SJ Park
2026-07-06 14:06 ` [PATCH 01/11] mm/damon/core: stop ctxs in damon_start() before returning an error SJ Park
2026-07-06 14:06 ` [PATCH 02/11] samples/damon/mtier: do not stop first context for damon_start() failure SJ Park
2026-07-06 14:06 ` [PATCH 03/11] mm/damon/core: make damon_stop() never fails SJ Park
2026-07-06 14:06 ` [PATCH 04/11] mm/damon/sysfs: ignore damon_stop() return value SJ Park
2026-07-06 14:06 ` [PATCH 05/11] mm/damon/reclaaim: " SJ Park
2026-07-06 14:06 ` [PATCH 06/11] mm/damon/lru_sort: " SJ Park
2026-07-06 14:06 ` [PATCH 07/11] mm/damon/core: change damon_stop() return type to void SJ Park
2026-07-06 14:06 ` [PATCH 08/11] samples/damon/mtier: stop all contexts with single damon_stop() call SJ Park
2026-07-06 14:06 ` SJ Park [this message]
2026-07-06 14:06 ` [PATCH 10/11] samples/damon/wsse: do not stop ctx for damon_call() failure SJ Park
2026-07-06 14:06 ` [PATCH 11/11] samples/damon/prcl: do not stop DAMON " 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=20260706140628.87414-10-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=damon@lists.linux.dev \
--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