cxl: Fix kobject memleak
authorWang Hai <wanghai38@huawei.com>
Tue, 2 Jun 2020 12:07:33 +0000 (20:07 +0800)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Mon, 29 Jun 2020 16:12:53 +0000 (18:12 +0200)
Currently the error return path from kobject_init_and_add() is not
followed by a call to kobject_put() - which means we are leaking
the kobject.

Fix it by adding a call to kobject_put() in the error path of
kobject_init_and_add().

Fixes: b087e6190ddc ("cxl: Export optional AFU configuration record in sysfs")
Reported-by: Hulk Robot <hulkci@huawei.com>
Signed-off-by: Wang Hai <wanghai38@huawei.com>
Acked-by: Andrew Donnellan <ajd@linux.ibm.com>
Acked-by: Frederic Barrat <fbarrat@linux.ibm.com>
Link: https://lore.kernel.org/r/20200602120733.5943-1-wanghai38@huawei.com
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
drivers/misc/cxl/sysfs.c

index f0263d1a1fdf270facb6c30b3403395d95cb635d..d97a243ad30c09f853d52b9ed084ecf1ed87ddfd 100644 (file)
@@ -624,7 +624,7 @@ static struct afu_config_record *cxl_sysfs_afu_new_cr(struct cxl_afu *afu, int c
        rc = kobject_init_and_add(&cr->kobj, &afu_config_record_type,
                                  &afu->dev.kobj, "cr%i", cr->cr);
        if (rc)
-               goto err;
+               goto err1;
 
        rc = sysfs_create_bin_file(&cr->kobj, &cr->config_attr);
        if (rc)