[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220811071844.74020-1-xhao@linux.alibaba.com>
Date: Thu, 11 Aug 2022 15:18:43 +0800
From: Xin Hao <xhao@...ux.alibaba.com>
To: cl@...ux.com
Cc: penberg@...nel.org, rientjes@...gle.com, iamjoonsoo.kim@....com,
42.hyeyoo@...il.com, akpm@...ux-foundation.org, vbabka@...e.cz,
roman.gushchin@...ux.dev, linux-mm@...ck.org,
linux-kernel@...r.kernel.org
Subject: [PATCH V2 0/1] mm/slub: release kobject if kobject_init_and_add failed in sysfs_slab_add
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
of s->kobj is leaked.
V1 -> V2
use kobject_put() instead kobject_del().
V1:
https://patchwork.kernel.org/project/linux-mm/patch/20220811025258.68684-1-xhao@linux.alibaba.com/
Xin Hao (1):
mm/slub: release kobject if kobject_init_and_add failed in
sysfs_slab_add
mm/slub.c | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)
--
2.31.0
Powered by blists - more mailing lists