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 9/9] mm/damon/sysfs: kobject_del() probe dirs
Date: Tue, 16 Jun 2026 18:11:45 -0700 [thread overview]
Message-ID: <20260617011146.97423-1-sj@kernel.org> (raw)
In-Reply-To: <20260616152411.AD0241F000E9@smtp.kernel.org>
On Tue, 16 Jun 2026 15:24:11 +0000 sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
>
> Pre-existing issues:
> - [Medium] The patch adds `kobject_del()` to `damon_sysfs_probes_rm_dirs()` to fix sysfs name collisions caused by delayed kobject releases, but misses the exact same flaw on the error paths of `damon_sysfs_probes_add_dirs()` and multiple other array-building functions. This leaves the system vulnerable to `-EEXIST` failures upon retry after an error.
> --
>
> commit 4a5efc2733f009261a15fd64a4d901ca19499bb5
> Author: SeongJae Park <sj@kernel.org>
>
> mm/damon/sysfs: kobject_del() probe dirs
>
> This commit fixes a directory creation failure caused by name conflicts
> when CONFIG_DEBUG_KOBJECT_RELEASE is enabled. It adds missing kobject_del()
> calls during the removal of probe directories.
>
> > diff --git a/mm/damon/sysfs.c b/mm/damon/sysfs.c
> > index 04725ff3d9f3c..04ca0a34e1206 100644
> > --- a/mm/damon/sysfs.c
> > +++ b/mm/damon/sysfs.c
> > @@ -1139,6 +1139,7 @@ static void damon_sysfs_probes_rm_dirs(
> >
> > for (i = 0; i < probes->nr; i++) {
> > damon_sysfs_probe_rm_dirs(probes_arr[i]);
> > + kobject_del(&probes_arr[i]->kobj);
>
> [Severity: Medium]
> This is a pre-existing issue, but it looks like the same lack of
> kobject_del() on error paths could cause name collisions upon retry.
>
> For example, if damon_sysfs_probe_add_dirs() fails inside
> damon_sysfs_probes_add_dirs(), the error path drops the probe by calling
> kobject_put() without kobject_del():
>
> mm/damon/sysfs.c:damon_sysfs_probes_add_dirs() {
> ...
> err = damon_sysfs_probe_add_dirs(probe);
> if (err) {
> kobject_put(&probe->kobj);
> damon_sysfs_probes_rm_dirs(probes);
> return err;
> }
> ...
> }
>
> Under CONFIG_DEBUG_KOBJECT_RELEASE, if userspace immediately retries the
> operation after an error, won't kobject_init_and_add() fail with -EEXIST due
> to a name collision with the lingering directory?
>
> Should we also add synchronous sysfs deletion via kobject_del() to these
> similar error paths?
> - mm/damon/sysfs.c:damon_sysfs_targets_add_dirs()
> - mm/damon/sysfs.c:damon_sysfs_contexts_add_dirs()
> - mm/damon/sysfs.c:damon_sysfs_kdamonds_add_dirs()
> - mm/damon/sysfs-schemes.c:damon_sysfs_schemes_add_dirs()
Yes. Sashiko reported same issues in other replies to this thread and I will
fix these in the next revision.
Thanks,
SJ
[...]
next prev parent reply other threads:[~2026-06-17 1:11 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-16 15:08 [RFC PATCH 0/9] mm/damon/sysfs: kobject_del() directories that users can create/remove SeongJae Park
2026-06-16 15:08 ` [RFC PATCH 1/9] mm/damon/sysfs: kobject_del() target, context and kdamond dirs SeongJae Park
2026-06-16 15:25 ` sashiko-bot
2026-06-17 0:02 ` SeongJae Park
2026-06-16 15:08 ` [RFC PATCH 2/9] mm/damon/sysfs: kobject_del() region dirs SeongJae Park
2026-06-16 15:29 ` sashiko-bot
2026-06-17 0:18 ` SeongJae Park
2026-06-16 15:08 ` [RFC PATCH 3/9] mm/damon/sysfs-schemes: kobject_del() scheme dirs SeongJae Park
2026-06-16 15:27 ` sashiko-bot
2026-06-17 0:52 ` SeongJae Park
2026-06-16 15:08 ` [RFC PATCH 4/9] mm/damon/sysfs-schemes: kobject_del() scheme region dirs SeongJae Park
2026-06-16 15:25 ` sashiko-bot
2026-06-17 0:43 ` SeongJae Park
2026-06-16 15:08 ` [RFC PATCH 5/9] mm/damon/sysfs-schemes: kobject_del() scheme filter dirs SeongJae Park
2026-06-16 15:08 ` [RFC PATCH 6/9] mm/damon/sysfs-schemes: kobject_del() scheme quota goal dirs SeongJae Park
2026-06-16 15:27 ` sashiko-bot
2026-06-17 0:55 ` SeongJae Park
2026-06-16 15:08 ` [RFC PATCH 7/9] mm/damon/sysfs-schemes: kobject_del() scheme action destination dirs SeongJae Park
2026-06-16 15:34 ` sashiko-bot
2026-06-17 1:07 ` SeongJae Park
2026-06-16 15:08 ` [RFC PATCH 8/9] mm/damon/sysfs: kobject_del() probe filter dirs SeongJae Park
2026-06-16 15:27 ` sashiko-bot
2026-06-17 1:10 ` SeongJae Park
2026-06-16 15:08 ` [RFC PATCH 9/9] mm/damon/sysfs: kobject_del() probe dirs SeongJae Park
2026-06-16 15:24 ` sashiko-bot
2026-06-17 1:11 ` SeongJae Park [this message]
2026-06-17 1:15 ` [RFC PATCH 0/9] mm/damon/sysfs: kobject_del() directories that users can create/remove 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=20260617011146.97423-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