From: SeongJae Park <sj@kernel.org>
To: sashiko-bot@kernel.org
Cc: SeongJae Park <sj@kernel.org>, damon@lists.linux.dev
Subject: Re: [RFC PATCH v2.2 10/28] mm/damon/sysfs: implement probe dir
Date: Fri, 15 May 2026 18:00:42 -0700 [thread overview]
Message-ID: <20260516010043.145317-1-sj@kernel.org> (raw)
In-Reply-To: <20260515010815.C6358C2BCB3@smtp.kernel.org>
On Fri, 15 May 2026 01:08:15 +0000 sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Low] The newly introduced kobj_type structure 'damon_sysfs_probe_ktype' is missing the 'static' keyword.
> --
>
> commit 6edcbcf176b612eae059c59f709c455cff251235
> Author: SeongJae Park <sj@kernel.org>
>
> mm/damon/sysfs: implement probe dir
>
> This commit implements a sysfs directory to let users install individual
> data probes.
>
> > diff --git a/mm/damon/sysfs.c b/mm/damon/sysfs.c
> > index 5f3b253f50ebf..c028e4b1281e6 100644
> > --- a/mm/damon/sysfs.c
> > +++ b/mm/damon/sysfs.c
>
> [ ... ]
>
> > +static struct attribute *damon_sysfs_probe_attrs[] = {
> > + NULL,
> > +};
> > +ATTRIBUTE_GROUPS(damon_sysfs_probe);
> > +
> > +const struct kobj_type damon_sysfs_probe_ktype = {
>
> This isn't a bug, but should damon_sysfs_probe_ktype be marked as static?
>
> It appears to only be used locally within this file, and omitting the
> static keyword will needlessly expose the symbol globally and might
> trigger warnings from static analysis tools.
Good finding. I will add 'static' keyword in the next revision.
Thanks,
SJ
[...]
next prev parent reply other threads:[~2026-05-16 1:00 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 0:44 [RFC PATCH v2.2 00/28] mm/damon: introduce data attributes monitoring SeongJae Park
2026-05-15 0:44 ` [RFC PATCH v2.2 01/28] mm/damon/core: introduce struct damon_probe SeongJae Park
2026-05-15 0:44 ` [RFC PATCH v2.2 02/28] mm/damon/core: embed damon_probe objects in damon_ctx SeongJae Park
2026-05-15 1:17 ` sashiko-bot
2026-05-15 22:58 ` SeongJae Park
2026-05-15 0:44 ` [RFC PATCH v2.2 03/28] mm/damon/core: introduce damon_filter SeongJae Park
2026-05-15 1:14 ` sashiko-bot
2026-05-16 0:11 ` SeongJae Park
2026-05-15 0:44 ` [RFC PATCH v2.2 04/28] mm/damon/core: commit probes SeongJae Park
2026-05-15 1:05 ` sashiko-bot
2026-05-16 0:23 ` SeongJae Park
2026-05-15 0:44 ` [RFC PATCH v2.2 05/28] mm/damon/core: introduce damon_region->probe_hits SeongJae Park
2026-05-15 0:54 ` sashiko-bot
2026-05-16 0:35 ` SeongJae Park
2026-05-15 0:44 ` [RFC PATCH v2.2 06/28] mm/damon/core: introduce damon_ops->apply_probes SeongJae Park
2026-05-15 0:53 ` sashiko-bot
2026-05-16 0:41 ` SeongJae Park
2026-05-15 0:44 ` [RFC PATCH v2.2 07/28] mm/damon/core: do data attributes monitoring SeongJae Park
2026-05-15 1:05 ` sashiko-bot
2026-05-16 0:46 ` SeongJae Park
2026-05-15 0:44 ` [RFC PATCH v2.2 08/28] mm/damon/paddr: support " SeongJae Park
2026-05-15 1:29 ` sashiko-bot
2026-05-16 0:56 ` SeongJae Park
2026-05-15 0:44 ` [RFC PATCH v2.2 09/28] mm/damon/sysfs: implement probes dir SeongJae Park
2026-05-15 0:44 ` [RFC PATCH v2.2 10/28] mm/damon/sysfs: implement probe dir SeongJae Park
2026-05-15 1:08 ` sashiko-bot
2026-05-16 1:00 ` SeongJae Park [this message]
2026-05-15 0:44 ` [RFC PATCH v2.2 11/28] mm/damon/sysfs: implement filters directory SeongJae Park
2026-05-15 0:44 ` [RFC PATCH v2.2 12/28] mm/damon/sysfs: implement filter dir SeongJae Park
2026-05-15 0:44 ` [RFC PATCH v2.2 13/28] mm/damon/sysfs: implement filter dir files SeongJae Park
2026-05-15 0:44 ` [RFC PATCH v2.2 14/28] mm/damon/sysfs: setup probes on DAMON core API parameters SeongJae Park
2026-05-15 0:44 ` [RFC PATCH v2.2 15/28] mm/damon/sysfs-schemes: implement tried_regions/<r>/probes/ SeongJae Park
2026-05-15 1:27 ` sashiko-bot
2026-05-16 1:27 ` SeongJae Park
2026-05-15 0:44 ` [RFC PATCH v2.2 16/28] mm/damon/sysfs-schemes: implement probe dir SeongJae Park
2026-05-15 0:44 ` [RFC PATCH v2.2 17/28] mm/damon/sysfs-schemes: implement probe/hits file SeongJae Park
2026-05-15 0:44 ` [RFC PATCH v2.2 18/28] mm/damon: trace probe_hits SeongJae Park
2026-05-15 0:44 ` [RFC PATCH v2.2 19/28] selftests/damon/sysfs.sh: test probes dir SeongJae Park
2026-05-15 0:44 ` [RFC PATCH v2.2 20/28] Docs/mm/damon/design: document data attributes monitoring SeongJae Park
2026-05-15 0:44 ` [RFC PATCH v2.2 21/28] Docs/admin-guide/mm/damon/usage: " SeongJae Park
2026-05-15 1:06 ` sashiko-bot
2026-05-16 1:40 ` SeongJae Park
2026-05-15 0:44 ` [RFC PATCH v2.2 22/28] mm/damon/core: introduce DAMON_FILTER_TYPE_MEMCG SeongJae Park
2026-05-15 1:22 ` sashiko-bot
2026-05-16 1:45 ` SeongJae Park
2026-05-15 0:44 ` [RFC PATCH v2.2 23/28] mm/damon/paddr: support DAMON_FILTER_TYPE_MEMCG SeongJae Park
2026-05-15 0:44 ` [RFC PATCH v2.2 24/28] mm/damon/sysfs: add filters/<F>/path file SeongJae Park
2026-05-15 1:35 ` sashiko-bot
2026-05-16 1:47 ` SeongJae Park
2026-05-15 0:44 ` [RFC PATCH v2.2 25/28] mm/damon/sysfs-schemes: move memcg_path_to_id() to sysfs-common SeongJae Park
2026-05-15 1:24 ` sashiko-bot
2026-05-16 1:50 ` SeongJae Park
2026-05-15 0:44 ` [RFC PATCH v2.2 26/28] mm/damon/sysfs: setup damon_filter->memcg_id from path SeongJae Park
2026-05-15 0:44 ` [RFC PATCH v2.2 27/28] Docs/mm/damon/design: update for memcg damon filter SeongJae Park
2026-05-15 0:44 ` [RFC PATCH v2.2 28/28] Docs/admin-guide/mm/damon/usage: " 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=20260516010043.145317-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox