From: Andrew Morton <akpm@linux-foundation.org>
To: SJ Park <sj@kernel.org>
Cc: "# 6 . 14 . x" <stable@vger.kernel.org>,
damon@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH 0/6] samples/damon: handle damon_{start,stop}() failures
Date: Sun, 28 Jun 2026 21:49:00 -0700 [thread overview]
Message-ID: <20260628214900.243ae17b910c18a4434036d7@linux-foundation.org> (raw)
In-Reply-To: <20260628215447.96166-1-sj@kernel.org>
On Sun, 28 Jun 2026 14:54:39 -0700 SJ Park <sj@kernel.org> wrote:
> 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. wsse and prcl also have a problem in
> their damon_call() failure handling. As a result, memory leaks, next
> DAMON operation disruptions, and use-after-free can happen. Fix those.
>
> Note that only the damon_start() failure caused issues can reliably be
> reproduced. Reproducing those issues require the admin permission,
> though.
So it doesn't seem that we need to fast-track all this into 7.2-rcX?
prev parent reply other threads:[~2026-06-29 4:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-28 21:54 [PATCH 0/6] samples/damon: handle damon_{start,stop}() failures SJ Park
2026-06-28 21:54 ` [PATCH 1/6] samples/damon/wsse: handle damon_start() failure SJ Park
2026-06-28 21:54 ` [PATCH 2/6] samples/damon/prcl: " SJ Park
2026-06-28 21:54 ` [PATCH 3/6] samples/damon/mtier: " SJ Park
2026-06-28 21:54 ` [PATCH 4/6] samples/damon/mtier: handle damon_stop() failure SJ Park
2026-06-28 21:54 ` [PATCH 5/6] samples/damon/wsse: stop and free damon ctx when damon_call() fails SJ Park
2026-06-28 21:54 ` [PATCH 6/6] samples/damon/prcl: " SJ Park
2026-06-29 4:49 ` Andrew Morton [this message]
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=20260628214900.243ae17b910c18a4434036d7@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