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 6/9] mm/damon/sysfs-schemes: kobject_del() scheme quota goal dirs
Date: Tue, 16 Jun 2026 17:55:07 -0700 [thread overview]
Message-ID: <20260617005507.96990-1-sj@kernel.org> (raw)
In-Reply-To: <20260616152729.369181F00A3D@smtp.kernel.org>
On Tue, 16 Jun 2026 15:27:28 +0000 sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
>
> Pre-existing issues:
> - [High] Missing Kobject Deletion on Error Path
> --
>
> commit b01a934762aa810a11a4a01efdd70c41f7274410
> Author: SeongJae Park <sj@kernel.org>
>
> mm/damon/sysfs-schemes: kobject_del() scheme quota goal dirs
>
> This commit adds missing kobject_del() calls to the cleanup of scheme quota
> goal directories. This prevents directory creation failures due to name
> conflicts when CONFIG_DEBUG_KOBJECT_RELEASE is enabled.
>
> > diff --git a/mm/damon/sysfs-schemes.c b/mm/damon/sysfs-schemes.c
> > index 300930c2c5b3f..737638be84f15 100644
> > --- a/mm/damon/sysfs-schemes.c
> > +++ b/mm/damon/sysfs-schemes.c
> > @@ -1465,8 +1465,10 @@ static void damos_sysfs_quota_goals_rm_dirs(
> > struct damos_sysfs_quota_goal **goals_arr = goals->goals_arr;
> > int i;
> >
> > - for (i = 0; i < goals->nr; i++)
> > + for (i = 0; i < goals->nr; i++) {
> > + kobject_del(&goals_arr[i]->kobj);
> > kobject_put(&goals_arr[i]->kobj);
> > + }
>
> [Severity: High]
> This isn't a bug introduced by this patch, but since you are fixing missing
> kobject_del() calls here to prevent name collisions, do the error paths in the
> various *_add_dirs() functions need similar fixes?
>
> If an error occurs after a successful kobject_init_and_add(), the error paths
> currently call kobject_put() without kobject_del(). This can leave the sysfs
> directory present until the object's reference count drops to zero and the
> delayed release runs, potentially causing a -EEXIST failure if a user retries
> the operation.
>
> For example, looking at damon_sysfs_targets_add_dirs() in mm/damon/sysfs.c:
>
> err = damon_sysfs_target_add_dirs(target);
> if (err)
> goto out;
> ...
> out:
> damon_sysfs_targets_rm_dirs(targets);
> kobject_put(&target->kobj);
> return err;
>
> Could this leak the sysfs directory for target->kobj?
>
> The identical pattern appears in several other error paths:
> - damon_sysfs_contexts_add_dirs() in mm/damon/sysfs.c
> - damon_sysfs_kdamonds_add_dirs() in mm/damon/sysfs.c
> - damon_sysfs_schemes_add_dirs() in mm/damon/sysfs-schemes.c
> - damos_sysfs_populate_region_dir() in mm/damon/sysfs-schemes.c
Good finding but Sashiko reported this in another reply to this thread, and I
promised to fix those in the next revision.
Thanks,
SJ
[...]
next prev parent reply other threads:[~2026-06-17 0:55 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 [this message]
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
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=20260617005507.96990-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