From: SeongJae Park <sj@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: SeongJae Park <sj@kernel.org>,
"# 6 . 14 . x" <stable@vger.kernel.org>,
damon@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: [PATCH 0/2] mm/damon/core: fix damon_call()/damos_walk() vs kdmond exit race
Date: Fri, 27 Mar 2026 16:33:13 -0700 [thread overview]
Message-ID: <20260327233319.3528-1-sj@kernel.org> (raw)
damon_call() and damos_walk() can leak memory and/or deadlock when they
race with kdamond terminations. Fix those.
Changes from RFC v3
(https://lore.kernel.org/20260327142605.4834-1-sj@kernel.org)
- Drop RFC tag.
- Rebase to latest mm-new.
Changes from RFC v2
(https://lore.kernel.org/20260327004952.58266-1-sj@kernel.org)
- Update and wordsmith commit message.
- Add damos_walk() race fix.
Changes from RFC v1
(https://lore.kernel.org/20260326062347.88569-3-sj@kernel.org)
- Clarify damon_call() call condition.
- Init call_controls_obsolete before kdamond_started completion.
- Wordsmith commit message.
- Split out repeat_call_control leak fix from the series.
SeongJae Park (2):
mm/damon/core: fix damon_call() vs kdamond_fn() exit race
mm/damon/core: fix damos_walk() vs kdamond_fn() exit race
include/linux/damon.h | 2 ++
mm/damon/core.c | 66 ++++++++++++++++++-------------------------
2 files changed, 30 insertions(+), 38 deletions(-)
base-commit: 305aff97ab8306284a0aa85f9128403b50c89019
--
2.47.3
next reply other threads:[~2026-03-27 23:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-27 23:33 SeongJae Park [this message]
2026-03-27 23:33 ` [PATCH 1/2] mm/damon/core: fix damon_call() vs kdamond_fn() exit race SeongJae Park
2026-03-28 0:43 ` (sashiko review) " SeongJae Park
2026-03-28 0:51 ` SeongJae Park
2026-03-27 23:33 ` [PATCH 2/2] mm/damon/core: fix damos_walk() " SeongJae Park
2026-03-28 0:42 ` (sashiko status) [PATCH 0/2] mm/damon/core: fix damon_call()/damos_walk() vs kdmond " 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=20260327233319.3528-1-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 \
--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