The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: SJ Park <sj@kernel.org>
Cc: SJ Park <sj@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	damon@lists.linux.dev, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org
Subject: [RFC PATCH v1.1 01/11] mm/damon/core: stop ctxs in damon_start() before returning an error
Date: Sun,  5 Jul 2026 09:01:28 -0700	[thread overview]
Message-ID: <20260705160142.97308-2-sj@kernel.org> (raw)
In-Reply-To: <20260705160142.97308-1-sj@kernel.org>

When multiple contexts are passed to damon_start(), the function starts
the contexts one by one.  If any of the operations fails, it immediately
returns an error.  Contexts that successfully started before the failure
keep running.  The caller should catch this and stop the contexts.  It
is complicated and easy to make mistakes.  Stop all contexts in
damon_start() under the failures.

Signed-off-by: SJ Park <sj@kernel.org>
---
 mm/damon/core.c | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/mm/damon/core.c b/mm/damon/core.c
index 3c5a46e1c079a..d89a7f2faf350 100644
--- a/mm/damon/core.c
+++ b/mm/damon/core.c
@@ -1917,6 +1917,9 @@ int damon_start(struct damon_ctx **ctxs, int nr_ctxs, bool exclusive)
 		running_exclusive_ctxs = true;
 	mutex_unlock(&damon_lock);
 
+	if (i != nr_ctxs)
+		damon_stop(ctxs, i);
+
 	return err;
 }
 
-- 
2.47.3

  reply	other threads:[~2026-07-05 16:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-05 16:01 [RFC PATCH v1.1 00/11] mm/damon: refactor damon_{start,stop,commit}() for simple error handling SJ Park
2026-07-05 16:01 ` SJ Park [this message]
2026-07-05 16:01 ` [RFC PATCH v1.1 02/11] samples/damon/mtier: do not stop first context for damon_start() failure SJ Park
2026-07-05 16:01 ` [RFC PATCH v1.1 03/11] mm/damon/core: make damon_stop() never fails SJ Park
2026-07-05 16:01 ` [RFC PATCH v1.1 04/11] mm/damon/sysfs: ignore damon_stop() return value SJ Park
2026-07-05 16:01 ` [RFC PATCH v1.1 05/11] mm/damon/reclaaim: " SJ Park
2026-07-05 16:01 ` [RFC PATCH v1.1 06/11] mm/damon/lru_sort: " SJ Park
2026-07-05 16:01 ` [RFC PATCH v1.1 07/11] mm/damon/core: change damon_stop() return type to void SJ Park
2026-07-05 16:01 ` [RFC PATCH v1.1 08/11] samples/damon/mtier: stop all contexts with single damon_stop() call SJ Park
2026-07-05 16:01 ` [RFC PATCH v1.1 09/11] mm/damon/core: wait ctx stop in damon_call() before reruning an error SJ Park
2026-07-05 16:01 ` [RFC PATCH v1.1 10/11] samples/damon/wsse: do not stop ctx for damon_call() failure SJ Park
2026-07-05 16:01 ` [RFC PATCH v1.1 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=20260705160142.97308-2-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