From: SJ Park <sj@kernel.org>
To: sashiko-bot@kernel.org
Cc: SJ Park <sj@kernel.org>, damon@lists.linux.dev
Subject: Re: [PATCH 05/17] mm/damon/core: introduce damon_prep struct
Date: Mon, 31 Aug 2026 22:01:49 -0700 [thread overview]
Message-ID: <20260901050151.3659-1-sj@kernel.org> (raw)
In-Reply-To: <20260901044601.B5FCA1F00A3D@smtp.kernel.org>
On Tue, 01 Sep 2026 04:46:01 +0000 sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Low] Missing exported cleanup API for `struct damon_prep` leads to broken abstraction on error paths.
> --
>
> commit 046989ba790c1b12be9fe4a07f46c502a62eeb7b
> Author: SJ Park <sj@kernel.org>
>
> mm/damon/core: introduce damon_prep struct
>
> This commit introduces the damon_prep data structure to specify preparatory
> actions for DAMON probes. It also adds DAMON_PREP_SET_PGIDLE as the initial
> preparation action for access monitoring.
>
> > diff --git a/mm/damon/core.c b/mm/damon/core.c
> > index 644daf5a16560..0b396c2456d05 100644
> > --- a/mm/damon/core.c
> > +++ b/mm/damon/core.c
>
> [ ... ]
>
> > @@ -111,6 +111,28 @@ int damon_select_ops(struct damon_ctx *ctx, enum damon_ops_id id)
> > return err;
> > }
> >
> > +struct damon_prep *damon_new_prep(enum damon_prep_action action)
> > +{
> > + struct damon_prep *prep;
> > +
> > + prep = kmalloc_obj(*prep);
> > + if (!prep)
> > + return NULL;
> > + prep->action = action;
> > + INIT_LIST_HEAD(&prep->list);
> > + return prep;
> > +}
>
> [Severity: Low]
> Is there a missing exported cleanup API for struct damon_prep?
>
> Since damon_new_prep() is exposed for external modules to allocate a new
> prep structure, do they need a corresponding exported destructor (like
> damon_destroy_prep()) to clean it up if an error occurs before it is
> attached to a probe via damon_add_prep()?
>
> Currently, damon_free_prep() is static, which forces any external caller to
> manually call kfree() on error paths, potentially breaking the subsystem's
> abstraction.
The cleanup API is not necessary. Callers will be able to free up preps with
the context at once using damon_destroy_ctx().
>
> > +
> > +void damon_add_prep(struct damon_probe *p, struct damon_prep *prep)
> > +{
> > + list_add_tail(&prep->list, &p->preps);
> > +}
> > +
> > +static void damon_free_prep(struct damon_prep *p)
> > +{
> > + kfree(p);
> > +}
>
> --
> Sashiko AI review · https://sashiko.dev/#/patchset/20260901043417.2165-1-sj@kernel.org?part=5
Thanks,
SJ
next prev parent reply other threads:[~2026-09-01 5:01 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-01 4:33 [PATCH 00/17] mm/damon: introduce data access-as-a-data attribute SJ Park
2026-09-01 4:33 ` [PATCH 01/17] mm/damon/core: introduce DAMON_FILTER_TYPE_PGIDLE_UNSET SJ Park
2026-09-01 4:41 ` sashiko-bot
2026-09-01 4:33 ` [PATCH 02/17] mm/damon/paddr: support PGIDLE_UNSET probe filter type SJ Park
2026-09-01 4:41 ` sashiko-bot
2026-09-01 4:33 ` [PATCH 03/17] mm/damon/sysfs: support pgidle_unset " SJ Park
2026-09-01 4:42 ` sashiko-bot
2026-09-01 4:34 ` [PATCH 04/17] Docs/mm/damon/design: document " SJ Park
2026-09-01 4:35 ` sashiko-bot
2026-09-01 4:34 ` [PATCH 05/17] mm/damon/core: introduce damon_prep struct SJ Park
2026-09-01 4:46 ` sashiko-bot
2026-09-01 5:01 ` SJ Park [this message]
2026-09-01 4:34 ` [PATCH 06/17] mm/damon/core: commit preps SJ Park
2026-09-01 4:43 ` sashiko-bot
2026-09-01 4:34 ` [PATCH 07/17] mm/damon/core: introduce damon_operations->prep_probes() SJ Park
2026-09-01 4:40 ` sashiko-bot
2026-09-01 4:34 ` [PATCH 08/17] mm/damon/paddr: support damon_prep SJ Park
2026-09-01 4:47 ` sashiko-bot
2026-09-01 5:05 ` SJ Park
2026-09-01 4:34 ` [PATCH 09/17] mm/damon/sysfs: implement preps directory SJ Park
2026-09-01 4:40 ` sashiko-bot
2026-09-01 4:34 ` [PATCH 10/17] mm/damon/sysfs: implement preps/nr_preps file SJ Park
2026-09-01 4:42 ` sashiko-bot
2026-09-01 4:34 ` [PATCH 11/17] mm/damon/sysfs: create directories for nr_preps writes SJ Park
2026-09-01 4:40 ` sashiko-bot
2026-09-01 4:34 ` [PATCH 12/17] mm/damon/sysfs: implement prep_action file SJ Park
2026-09-01 4:40 ` sashiko-bot
2026-09-01 4:34 ` [PATCH 13/17] mm/damon/sysfs: pass preps to DAMON core SJ Park
2026-09-01 4:53 ` sashiko-bot
2026-09-01 5:24 ` SJ Park
2026-09-01 4:34 ` [PATCH 14/17] selftests/damon/sysfs.sh: test probe prep sysfs files SJ Park
2026-09-01 4:36 ` sashiko-bot
2026-09-01 4:34 ` [PATCH 15/17] Docs/mm/damon/design: document probe preps SJ Park
2026-09-01 4:35 ` sashiko-bot
2026-09-01 4:34 ` [PATCH 16/17] Docs/admin-guide/mm/damon/usage: document probe preps sysfs files SJ Park
2026-09-01 4:38 ` sashiko-bot
2026-09-01 4:34 ` [PATCH 17/17] Docs/ABI/damon: document probe prep " SJ Park
2026-09-01 4:36 ` sashiko-bot
2026-09-01 5:26 ` [PATCH 00/17] mm/damon: introduce data access-as-a-data attribute 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=20260901050151.3659-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=damon@lists.linux.dev \
--cc=sashiko-bot@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.