From: SeongJae Park <sj@kernel.org>
Cc: SeongJae Park <sj@kernel.org>,
"# 6 . 14 . x" <stable@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
damon@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: [RFC PATCH v3 0/4] samples/damon: handle damon_{start,stop}() failures
Date: Tue, 9 Jun 2026 18:14:13 -0700 [thread overview]
Message-ID: <20260610011420.3018-1-sj@kernel.org> (raw)
All DAMON sample modules are not correctly handling failures from
damon_start(). Among those, mtier also has an additional problem for
handling of damon_stop() failures. As a result, memory leaks, next
DAMON operation disruptions, and use-after-free can happen. Fix those.
Changes from RFC v2
- RFC v2: https://lore.kernel.org/20260609142119.68120-1-sj@kernel.org
- Add damon_start() failure handling fix for wsse and prcl.
Changes from RFC v1
- RFC v1: https://lore.kernel.org/20260609005443.2122-1-sj@kernel.org
- Add damon_stop() failure handling fix to the series.
SeongJae Park (4):
samples/damon/wsse: handle damon_start() failure
samples/damon/prcl: handle damon_start() failure
samples/damon/mtier: handle damon_start() failure
samples/damon/mtier: handle damon_stop() failure
samples/damon/mtier.c | 14 ++++++++++++--
samples/damon/prcl.c | 4 +++-
samples/damon/wsse.c | 4 +++-
3 files changed, 18 insertions(+), 4 deletions(-)
base-commit: e38932476396c4da618a9e904ba4e45f1891d910
--
2.47.3
next reply other threads:[~2026-06-10 1:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-10 1:14 SeongJae Park [this message]
2026-06-10 1:14 ` [RFC PATCH v3 1/4] samples/damon/wsse: handle damon_start() failure SeongJae Park
2026-06-10 1:29 ` sashiko-bot
2026-06-10 3:48 ` SeongJae Park
2026-06-10 1:14 ` [RFC PATCH v3 2/4] samples/damon/prcl: " SeongJae Park
2026-06-10 1:29 ` sashiko-bot
2026-06-10 3:52 ` SeongJae Park
2026-06-10 1:14 ` [RFC PATCH v3 3/4] samples/damon/mtier: " SeongJae Park
2026-06-10 1:14 ` [RFC PATCH v3 4/4] samples/damon/mtier: handle damon_stop() failure 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=20260610011420.3018-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.