From: Hyeonggon Yoo <42.hyeyoo@gmail.com>
To: Xin Hao <xhao@linux.alibaba.com>
Cc: cl@linux.com, penberg@kernel.org, rientjes@google.com,
iamjoonsoo.kim@lge.com, akpm@linux-foundation.org,
vbabka@suse.cz, roman.gushchin@linux.dev, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/slub: release kobject if kobject_init_and_add failed in sysfs_slab_add
Date: Thu, 11 Aug 2022 03:31:38 +0000 [thread overview]
Message-ID: <YvR4GqAqykjUwBJn@ip-172-31-24-42.ap-northeast-1.compute.internal> (raw)
In-Reply-To: <20220811025258.68684-1-xhao@linux.alibaba.com>
On Thu, Aug 11, 2022 at 10:52:58AM +0800, Xin Hao wrote:
> In kobject_init_and_add() function, the refcount is setted by calling
> kobject_init() function, regardless of whether the return value is zero
> or not, therefore, we must call kobject_del(&s->kobj) to prevent memory
Hello and thanks!
Should kobject_del() be called when kobject_add() failed?
its comments says:
597 * kobject_del() - Unlink kobject from hierarchy.
598 * @kobj: object.
599 *
600 * This is the function that should be called to delete an object
601 * successfully added via kobject_add().
AFAIK kobject_put() is proper function to call when
kobject_init_and_add() failed as stated in its comment:
417 /**
418 * kobject_init_and_add() - Initialize a kobject structure and add it to
419 * the kobject hierarchy.
420 * @kobj: pointer to the kobject to initialize
421 * @ktype: pointer to the ktype for this kobject.
422 * @parent: pointer to the parent of this kobject.
423 * @fmt: the name of the kobject.
424 *
425 * This function combines the call to kobject_init() and kobject_add().
426 *
427 * If this function returns an error, kobject_put() must be called to
428 * properly clean up the memory associated with the object. This is the
429 * same type of error handling after a call to kobject_add() and kobject
430 * lifetime rules are the same here.
> of s->kobj is leaked.
>
> Signed-off-by: Xin Hao <xhao@linux.alibaba.com>
> ---
> mm/slub.c | 7 +++----
> 1 file changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/mm/slub.c b/mm/slub.c
> index b1281b8654bd..63b0a8a3a71f 100644
> --- a/mm/slub.c
> +++ b/mm/slub.c
> @@ -5981,19 +5981,18 @@ static int sysfs_slab_add(struct kmem_cache *s)
>
> err = sysfs_create_group(&s->kobj, &slab_attr_group);
> if (err)
> - goto out_del_kobj;
> + goto out;
>
> if (!unmergeable) {
> /* Setup first alias */
> sysfs_slab_alias(s, s->name);
> }
> + return err;
> out:
> if (!unmergeable)
> kfree(name);
> - return err;
> -out_del_kobj:
> kobject_del(&s->kobj);
> - goto out;
> + return err;
> }
>
> void sysfs_slab_unlink(struct kmem_cache *s)
> --
> 2.31.0
next prev parent reply other threads:[~2022-08-11 3:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-11 2:52 Xin Hao
2022-08-11 3:31 ` Hyeonggon Yoo [this message]
2022-08-11 3:52 ` haoxin
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=YvR4GqAqykjUwBJn@ip-172-31-24-42.ap-northeast-1.compute.internal \
--to=42.hyeyoo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=vbabka@suse.cz \
--cc=xhao@linux.alibaba.com \
/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