[PATCH 00/11] fix memory leak while kset_register() fails
Yang Yingliang
yangyingliang at huawei.com
Fri Oct 21 13:20:51 AEDT 2022
The previous discussion link:
https://lore.kernel.org/lkml/0db486eb-6927-927e-3629-958f8f211194@huawei.com/T/
kset_register() is currently used in some places without calling
kset_put() in error path, because the callers think it should be
kset internal thing to do, but the driver core can not know what
caller doing with that memory at times. The memory could be freed
both in kset_put() and error path of caller, if it is called in
kset_register().
So make the function documentation more explicit about calling
kset_put() in the error path of caller first, so that people
have a chance to know what to do here, then fixes this leaks
by calling kset_put() from callers.
Liu Shixin (1):
ubifs: Fix memory leak in ubifs_sysfs_init()
Yang Yingliang (10):
kset: fix documentation for kset_register()
kset: add null pointer check in kset_put()
bus: fix possible memory leak in bus_register()
kobject: fix possible memory leak in kset_create_and_add()
class: fix possible memory leak in __class_register()
firmware: qemu_fw_cfg: fix possible memory leak in
fw_cfg_build_symlink()
f2fs: fix possible memory leak in f2fs_init_sysfs()
erofs: fix possible memory leak in erofs_init_sysfs()
ocfs2: possible memory leak in mlog_sys_init()
drm/amdgpu/discovery: fix possible memory leak
drivers/base/bus.c | 4 +++-
drivers/base/class.c | 6 ++++++
drivers/firmware/qemu_fw_cfg.c | 2 +-
drivers/gpu/drm/amd/amdgpu/amdgpu_discovery.c | 5 +++--
fs/erofs/sysfs.c | 4 +++-
fs/f2fs/sysfs.c | 4 +++-
fs/ocfs2/cluster/masklog.c | 7 ++++++-
fs/ubifs/sysfs.c | 2 ++
include/linux/kobject.h | 3 ++-
lib/kobject.c | 5 ++++-
10 files changed, 33 insertions(+), 9 deletions(-)
--
2.25.1
More information about the Linux-erofs
mailing list