All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yang Yingliang <yangyingliang@huawei.com>
To: <linux-kernel@vger.kernel.org>, <qemu-devel@nongnu.org>,
	<linux-f2fs-devel@lists.sourceforge.net>,
	<linux-erofs@lists.ozlabs.org>, <ocfs2-devel@oss.oracle.com>,
	<linux-mtd@lists.infradead.org>, <amd-gfx@lists.freedesktop.org>
Cc: <gregkh@linuxfoundation.org>, <rafael@kernel.org>,
	<somlo@cmu.edu>, <mst@redhat.com>, <jaegeuk@kernel.org>,
	<chao@kernel.org>, <hsiangkao@linux.alibaba.com>,
	<huangjianan@oppo.com>, <mark@fasheh.com>, <jlbec@evilplan.org>,
	<joseph.qi@linux.alibaba.com>, <akpm@linux-foundation.org>,
	<alexander.deucher@amd.com>, <luben.tuikov@amd.com>,
	<richard@nod.at>, <liushixin2@huawei.com>
Subject: [PATCH 04/11] kobject: fix possible memory leak in kset_create_and_add()
Date: Fri, 21 Oct 2022 10:20:55 +0800	[thread overview]
Message-ID: <20221021022102.2231464-5-yangyingliang@huawei.com> (raw)
In-Reply-To: <20221021022102.2231464-1-yangyingliang@huawei.com>

Inject fault while loading module (e.g. qemu_fw_cfg.ko), kset_register()
may fail in kset_create_and_add(), if it fails, but the refcount of kobject
is not decreased to 0, the name allocated in kset_create() is leaked. To fix
this by calling kset_put(), so that name can be freed in callback function
kobject_cleanup() and kset can be freed in kset_release().

unreferenced object 0xffff888103cc8c08 (size 8):
  comm "modprobe", pid 508, jiffies 4294915182 (age 120.020s)
  hex dump (first 8 bytes):
    62 79 5f 6e 61 6d 65 00                          by_name.
  backtrace:
    [<00000000572f97f9>] __kmalloc_track_caller+0x1ae/0x320
    [<00000000a167a5cc>] kstrdup+0x3a/0x70
    [<000000001cd0d05e>] kstrdup_const+0x68/0x80
    [<00000000b9101e6d>] kvasprintf_const+0x10b/0x190
    [<0000000088f2b8df>] kobject_set_name_vargs+0x56/0x150
    [<000000003f8aca68>] kobject_set_name+0xab/0xe0
    [<00000000249f7816>] kset_create_and_add+0x72/0x200

Fixes: b727c702896f ("kset: add kset_create_and_add function")
Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
---
 lib/kobject.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lib/kobject.c b/lib/kobject.c
index 6da04353d974..e77f37200876 100644
--- a/lib/kobject.c
+++ b/lib/kobject.c
@@ -985,7 +985,7 @@ struct kset *kset_create_and_add(const char *name,
 		return NULL;
 	error = kset_register(kset);
 	if (error) {
-		kfree(kset);
+		kset_put(kset);
 		return NULL;
 	}
 	return kset;
-- 
2.25.1


WARNING: multiple messages have this Message-ID (diff)
From: Yang Yingliang via Ocfs2-devel <ocfs2-devel@oss.oracle.com>
To: <linux-kernel@vger.kernel.org>, <qemu-devel@nongnu.org>,
	<linux-f2fs-devel@lists.sourceforge.net>,
	<linux-erofs@lists.ozlabs.org>, <ocfs2-devel@oss.oracle.com>,
	<linux-mtd@lists.infradead.org>, <amd-gfx@lists.freedesktop.org>
Cc: alexander.deucher@amd.com, richard@nod.at, mst@redhat.com,
	gregkh@linuxfoundation.org, somlo@cmu.edu, chao@kernel.org,
	huangjianan@oppo.com, liushixin2@huawei.com,
	luben.tuikov@amd.com, hsiangkao@linux.alibaba.com,
	rafael@kernel.org, jaegeuk@kernel.org
Subject: [Ocfs2-devel] [PATCH 04/11] kobject: fix possible memory leak in kset_create_and_add()
Date: Fri, 21 Oct 2022 10:20:55 +0800	[thread overview]
Message-ID: <20221021022102.2231464-5-yangyingliang@huawei.com> (raw)
In-Reply-To: <20221021022102.2231464-1-yangyingliang@huawei.com>

Inject fault while loading module (e.g. qemu_fw_cfg.ko), kset_register()
may fail in kset_create_and_add(), if it fails, but the refcount of kobject
is not decreased to 0, the name allocated in kset_create() is leaked. To fix
this by calling kset_put(), so that name can be freed in callback function
kobject_cleanup() and kset can be freed in kset_release().

unreferenced object 0xffff888103cc8c08 (size 8):
  comm "modprobe", pid 508, jiffies 4294915182 (age 120.020s)
  hex dump (first 8 bytes):
    62 79 5f 6e 61 6d 65 00                          by_name.
  backtrace:
    [<00000000572f97f9>] __kmalloc_track_caller+0x1ae/0x320
    [<00000000a167a5cc>] kstrdup+0x3a/0x70
    [<000000001cd0d05e>] kstrdup_const+0x68/0x80
    [<00000000b9101e6d>] kvasprintf_const+0x10b/0x190
    [<0000000088f2b8df>] kobject_set_name_vargs+0x56/0x150
    [<000000003f8aca68>] kobject_set_name+0xab/0xe0
    [<00000000249f7816>] kset_create_and_add+0x72/0x200

Fixes: b727c702896f ("kset: add kset_create_and_add function")
Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
---
 lib/kobject.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lib/kobject.c b/lib/kobject.c
index 6da04353d974..e77f37200876 100644
--- a/lib/kobject.c
+++ b/lib/kobject.c
@@ -985,7 +985,7 @@ struct kset *kset_create_and_add(const char *name,
 		return NULL;
 	error = kset_register(kset);
 	if (error) {
-		kfree(kset);
+		kset_put(kset);
 		return NULL;
 	}
 	return kset;
-- 
2.25.1


_______________________________________________
Ocfs2-devel mailing list
Ocfs2-devel@oss.oracle.com
https://oss.oracle.com/mailman/listinfo/ocfs2-devel

WARNING: multiple messages have this Message-ID (diff)
From: Yang Yingliang via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: <linux-kernel@vger.kernel.org>, <qemu-devel@nongnu.org>,
	<linux-f2fs-devel@lists.sourceforge.net>,
	<linux-erofs@lists.ozlabs.org>, <ocfs2-devel@oss.oracle.com>,
	<linux-mtd@lists.infradead.org>, <amd-gfx@lists.freedesktop.org>
Cc: alexander.deucher@amd.com, richard@nod.at, mst@redhat.com,
	gregkh@linuxfoundation.org, somlo@cmu.edu, liushixin2@huawei.com,
	joseph.qi@linux.alibaba.com, luben.tuikov@amd.com,
	jlbec@evilplan.org, hsiangkao@linux.alibaba.com,
	rafael@kernel.org, jaegeuk@kernel.org, akpm@linux-foundation.org,
	mark@fasheh.com
Subject: [f2fs-dev] [PATCH 04/11] kobject: fix possible memory leak in kset_create_and_add()
Date: Fri, 21 Oct 2022 10:20:55 +0800	[thread overview]
Message-ID: <20221021022102.2231464-5-yangyingliang@huawei.com> (raw)
In-Reply-To: <20221021022102.2231464-1-yangyingliang@huawei.com>

Inject fault while loading module (e.g. qemu_fw_cfg.ko), kset_register()
may fail in kset_create_and_add(), if it fails, but the refcount of kobject
is not decreased to 0, the name allocated in kset_create() is leaked. To fix
this by calling kset_put(), so that name can be freed in callback function
kobject_cleanup() and kset can be freed in kset_release().

unreferenced object 0xffff888103cc8c08 (size 8):
  comm "modprobe", pid 508, jiffies 4294915182 (age 120.020s)
  hex dump (first 8 bytes):
    62 79 5f 6e 61 6d 65 00                          by_name.
  backtrace:
    [<00000000572f97f9>] __kmalloc_track_caller+0x1ae/0x320
    [<00000000a167a5cc>] kstrdup+0x3a/0x70
    [<000000001cd0d05e>] kstrdup_const+0x68/0x80
    [<00000000b9101e6d>] kvasprintf_const+0x10b/0x190
    [<0000000088f2b8df>] kobject_set_name_vargs+0x56/0x150
    [<000000003f8aca68>] kobject_set_name+0xab/0xe0
    [<00000000249f7816>] kset_create_and_add+0x72/0x200

Fixes: b727c702896f ("kset: add kset_create_and_add function")
Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
---
 lib/kobject.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lib/kobject.c b/lib/kobject.c
index 6da04353d974..e77f37200876 100644
--- a/lib/kobject.c
+++ b/lib/kobject.c
@@ -985,7 +985,7 @@ struct kset *kset_create_and_add(const char *name,
 		return NULL;
 	error = kset_register(kset);
 	if (error) {
-		kfree(kset);
+		kset_put(kset);
 		return NULL;
 	}
 	return kset;
-- 
2.25.1



_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

WARNING: multiple messages have this Message-ID (diff)
From: Yang Yingliang <yangyingliang@huawei.com>
To: <linux-kernel@vger.kernel.org>, <qemu-devel@nongnu.org>,
	<linux-f2fs-devel@lists.sourceforge.net>,
	<linux-erofs@lists.ozlabs.org>, <ocfs2-devel@oss.oracle.com>,
	<linux-mtd@lists.infradead.org>, <amd-gfx@lists.freedesktop.org>
Cc: <gregkh@linuxfoundation.org>, <rafael@kernel.org>,
	<somlo@cmu.edu>, <mst@redhat.com>, <jaegeuk@kernel.org>,
	<chao@kernel.org>, <hsiangkao@linux.alibaba.com>,
	<huangjianan@oppo.com>, <mark@fasheh.com>, <jlbec@evilplan.org>,
	<joseph.qi@linux.alibaba.com>, <akpm@linux-foundation.org>,
	<alexander.deucher@amd.com>, <luben.tuikov@amd.com>,
	<richard@nod.at>, <liushixin2@huawei.com>
Subject: [PATCH 04/11] kobject: fix possible memory leak in kset_create_and_add()
Date: Fri, 21 Oct 2022 10:20:55 +0800	[thread overview]
Message-ID: <20221021022102.2231464-5-yangyingliang@huawei.com> (raw)
In-Reply-To: <20221021022102.2231464-1-yangyingliang@huawei.com>

Inject fault while loading module (e.g. qemu_fw_cfg.ko), kset_register()
may fail in kset_create_and_add(), if it fails, but the refcount of kobject
is not decreased to 0, the name allocated in kset_create() is leaked. To fix
this by calling kset_put(), so that name can be freed in callback function
kobject_cleanup() and kset can be freed in kset_release().

unreferenced object 0xffff888103cc8c08 (size 8):
  comm "modprobe", pid 508, jiffies 4294915182 (age 120.020s)
  hex dump (first 8 bytes):
    62 79 5f 6e 61 6d 65 00                          by_name.
  backtrace:
    [<00000000572f97f9>] __kmalloc_track_caller+0x1ae/0x320
    [<00000000a167a5cc>] kstrdup+0x3a/0x70
    [<000000001cd0d05e>] kstrdup_const+0x68/0x80
    [<00000000b9101e6d>] kvasprintf_const+0x10b/0x190
    [<0000000088f2b8df>] kobject_set_name_vargs+0x56/0x150
    [<000000003f8aca68>] kobject_set_name+0xab/0xe0
    [<00000000249f7816>] kset_create_and_add+0x72/0x200

Fixes: b727c702896f ("kset: add kset_create_and_add function")
Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
---
 lib/kobject.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lib/kobject.c b/lib/kobject.c
index 6da04353d974..e77f37200876 100644
--- a/lib/kobject.c
+++ b/lib/kobject.c
@@ -985,7 +985,7 @@ struct kset *kset_create_and_add(const char *name,
 		return NULL;
 	error = kset_register(kset);
 	if (error) {
-		kfree(kset);
+		kset_put(kset);
 		return NULL;
 	}
 	return kset;
-- 
2.25.1


______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

WARNING: multiple messages have this Message-ID (diff)
From: Yang Yingliang via Linux-erofs <linux-erofs@lists.ozlabs.org>
To: <linux-kernel@vger.kernel.org>, <qemu-devel@nongnu.org>,
	<linux-f2fs-devel@lists.sourceforge.net>,
	<linux-erofs@lists.ozlabs.org>, <ocfs2-devel@oss.oracle.com>,
	<linux-mtd@lists.infradead.org>, <amd-gfx@lists.freedesktop.org>
Cc: alexander.deucher@amd.com, richard@nod.at, mst@redhat.com,
	gregkh@linuxfoundation.org, somlo@cmu.edu, huangjianan@oppo.com,
	liushixin2@huawei.com, joseph.qi@linux.alibaba.com,
	luben.tuikov@amd.com, jlbec@evilplan.org,
	hsiangkao@linux.alibaba.com, rafael@kernel.org,
	jaegeuk@kernel.org, akpm@linux-foundation.org, mark@fasheh.com
Subject: [PATCH 04/11] kobject: fix possible memory leak in kset_create_and_add()
Date: Fri, 21 Oct 2022 10:20:55 +0800	[thread overview]
Message-ID: <20221021022102.2231464-5-yangyingliang@huawei.com> (raw)
In-Reply-To: <20221021022102.2231464-1-yangyingliang@huawei.com>

Inject fault while loading module (e.g. qemu_fw_cfg.ko), kset_register()
may fail in kset_create_and_add(), if it fails, but the refcount of kobject
is not decreased to 0, the name allocated in kset_create() is leaked. To fix
this by calling kset_put(), so that name can be freed in callback function
kobject_cleanup() and kset can be freed in kset_release().

unreferenced object 0xffff888103cc8c08 (size 8):
  comm "modprobe", pid 508, jiffies 4294915182 (age 120.020s)
  hex dump (first 8 bytes):
    62 79 5f 6e 61 6d 65 00                          by_name.
  backtrace:
    [<00000000572f97f9>] __kmalloc_track_caller+0x1ae/0x320
    [<00000000a167a5cc>] kstrdup+0x3a/0x70
    [<000000001cd0d05e>] kstrdup_const+0x68/0x80
    [<00000000b9101e6d>] kvasprintf_const+0x10b/0x190
    [<0000000088f2b8df>] kobject_set_name_vargs+0x56/0x150
    [<000000003f8aca68>] kobject_set_name+0xab/0xe0
    [<00000000249f7816>] kset_create_and_add+0x72/0x200

Fixes: b727c702896f ("kset: add kset_create_and_add function")
Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
---
 lib/kobject.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lib/kobject.c b/lib/kobject.c
index 6da04353d974..e77f37200876 100644
--- a/lib/kobject.c
+++ b/lib/kobject.c
@@ -985,7 +985,7 @@ struct kset *kset_create_and_add(const char *name,
 		return NULL;
 	error = kset_register(kset);
 	if (error) {
-		kfree(kset);
+		kset_put(kset);
 		return NULL;
 	}
 	return kset;
-- 
2.25.1


WARNING: multiple messages have this Message-ID (diff)
From: Yang Yingliang via <qemu-devel@nongnu.org>
To: <linux-kernel@vger.kernel.org>, <qemu-devel@nongnu.org>,
	<linux-f2fs-devel@lists.sourceforge.net>,
	<linux-erofs@lists.ozlabs.org>, <ocfs2-devel@oss.oracle.com>,
	<linux-mtd@lists.infradead.org>, <amd-gfx@lists.freedesktop.org>
Cc: <gregkh@linuxfoundation.org>, <rafael@kernel.org>,
	<somlo@cmu.edu>, <mst@redhat.com>, <jaegeuk@kernel.org>,
	<chao@kernel.org>, <hsiangkao@linux.alibaba.com>,
	<huangjianan@oppo.com>, <mark@fasheh.com>, <jlbec@evilplan.org>,
	<joseph.qi@linux.alibaba.com>, <akpm@linux-foundation.org>,
	<alexander.deucher@amd.com>, <luben.tuikov@amd.com>,
	<richard@nod.at>, <liushixin2@huawei.com>
Subject: [PATCH 04/11] kobject: fix possible memory leak in kset_create_and_add()
Date: Fri, 21 Oct 2022 10:20:55 +0800	[thread overview]
Message-ID: <20221021022102.2231464-5-yangyingliang@huawei.com> (raw)
In-Reply-To: <20221021022102.2231464-1-yangyingliang@huawei.com>

Inject fault while loading module (e.g. qemu_fw_cfg.ko), kset_register()
may fail in kset_create_and_add(), if it fails, but the refcount of kobject
is not decreased to 0, the name allocated in kset_create() is leaked. To fix
this by calling kset_put(), so that name can be freed in callback function
kobject_cleanup() and kset can be freed in kset_release().

unreferenced object 0xffff888103cc8c08 (size 8):
  comm "modprobe", pid 508, jiffies 4294915182 (age 120.020s)
  hex dump (first 8 bytes):
    62 79 5f 6e 61 6d 65 00                          by_name.
  backtrace:
    [<00000000572f97f9>] __kmalloc_track_caller+0x1ae/0x320
    [<00000000a167a5cc>] kstrdup+0x3a/0x70
    [<000000001cd0d05e>] kstrdup_const+0x68/0x80
    [<00000000b9101e6d>] kvasprintf_const+0x10b/0x190
    [<0000000088f2b8df>] kobject_set_name_vargs+0x56/0x150
    [<000000003f8aca68>] kobject_set_name+0xab/0xe0
    [<00000000249f7816>] kset_create_and_add+0x72/0x200

Fixes: b727c702896f ("kset: add kset_create_and_add function")
Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
---
 lib/kobject.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lib/kobject.c b/lib/kobject.c
index 6da04353d974..e77f37200876 100644
--- a/lib/kobject.c
+++ b/lib/kobject.c
@@ -985,7 +985,7 @@ struct kset *kset_create_and_add(const char *name,
 		return NULL;
 	error = kset_register(kset);
 	if (error) {
-		kfree(kset);
+		kset_put(kset);
 		return NULL;
 	}
 	return kset;
-- 
2.25.1



WARNING: multiple messages have this Message-ID (diff)
From: Yang Yingliang <yangyingliang@huawei.com>
To: <linux-kernel@vger.kernel.org>, <qemu-devel@nongnu.org>,
	<linux-f2fs-devel@lists.sourceforge.net>,
	<linux-erofs@lists.ozlabs.org>, <ocfs2-devel@oss.oracle.com>,
	<linux-mtd@lists.infradead.org>, <amd-gfx@lists.freedesktop.org>
Cc: alexander.deucher@amd.com, richard@nod.at, mst@redhat.com,
	gregkh@linuxfoundation.org, somlo@cmu.edu, chao@kernel.org,
	huangjianan@oppo.com, liushixin2@huawei.com,
	joseph.qi@linux.alibaba.com, luben.tuikov@amd.com,
	jlbec@evilplan.org, hsiangkao@linux.alibaba.com,
	rafael@kernel.org, jaegeuk@kernel.org, akpm@linux-foundation.org,
	mark@fasheh.com
Subject: [PATCH 04/11] kobject: fix possible memory leak in kset_create_and_add()
Date: Fri, 21 Oct 2022 10:20:55 +0800	[thread overview]
Message-ID: <20221021022102.2231464-5-yangyingliang@huawei.com> (raw)
In-Reply-To: <20221021022102.2231464-1-yangyingliang@huawei.com>

Inject fault while loading module (e.g. qemu_fw_cfg.ko), kset_register()
may fail in kset_create_and_add(), if it fails, but the refcount of kobject
is not decreased to 0, the name allocated in kset_create() is leaked. To fix
this by calling kset_put(), so that name can be freed in callback function
kobject_cleanup() and kset can be freed in kset_release().

unreferenced object 0xffff888103cc8c08 (size 8):
  comm "modprobe", pid 508, jiffies 4294915182 (age 120.020s)
  hex dump (first 8 bytes):
    62 79 5f 6e 61 6d 65 00                          by_name.
  backtrace:
    [<00000000572f97f9>] __kmalloc_track_caller+0x1ae/0x320
    [<00000000a167a5cc>] kstrdup+0x3a/0x70
    [<000000001cd0d05e>] kstrdup_const+0x68/0x80
    [<00000000b9101e6d>] kvasprintf_const+0x10b/0x190
    [<0000000088f2b8df>] kobject_set_name_vargs+0x56/0x150
    [<000000003f8aca68>] kobject_set_name+0xab/0xe0
    [<00000000249f7816>] kset_create_and_add+0x72/0x200

Fixes: b727c702896f ("kset: add kset_create_and_add function")
Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
---
 lib/kobject.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lib/kobject.c b/lib/kobject.c
index 6da04353d974..e77f37200876 100644
--- a/lib/kobject.c
+++ b/lib/kobject.c
@@ -985,7 +985,7 @@ struct kset *kset_create_and_add(const char *name,
 		return NULL;
 	error = kset_register(kset);
 	if (error) {
-		kfree(kset);
+		kset_put(kset);
 		return NULL;
 	}
 	return kset;
-- 
2.25.1


  parent reply	other threads:[~2022-10-21  2:23 UTC|newest]

Thread overview: 216+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-21  2:20 [PATCH 00/11] fix memory leak while kset_register() fails Yang Yingliang
2022-10-21  2:20 ` Yang Yingliang
2022-10-21  2:20 ` Yang Yingliang via
2022-10-21  2:20 ` Yang Yingliang via Linux-erofs
2022-10-21  2:20 ` Yang Yingliang
2022-10-21  2:20 ` [f2fs-dev] " Yang Yingliang via Linux-f2fs-devel
2022-10-21  2:20 ` [Ocfs2-devel] " Yang Yingliang via Ocfs2-devel
2022-10-21  2:20 ` [PATCH 01/11] kset: fix documentation for kset_register() Yang Yingliang
2022-10-21  2:20   ` Yang Yingliang
2022-10-21  2:20   ` Yang Yingliang via
2022-10-21  2:20   ` Yang Yingliang via Linux-erofs
2022-10-21  2:20   ` Yang Yingliang
2022-10-21  2:20   ` [f2fs-dev] " Yang Yingliang via Linux-f2fs-devel
2022-10-21  2:20   ` [Ocfs2-devel] " Yang Yingliang via Ocfs2-devel
2022-10-21  5:34   ` Luben Tuikov
2022-10-21  5:34     ` [Ocfs2-devel] " Luben Tuikov via Ocfs2-devel
2022-10-21  5:34     ` [f2fs-dev] " Luben Tuikov via Linux-f2fs-devel
2022-10-21  5:34     ` Luben Tuikov
2022-10-21  5:34     ` Luben Tuikov via Linux-erofs
2022-10-21  5:34     ` Luben Tuikov
2022-10-21  8:05     ` Yang Yingliang
2022-10-21  8:05       ` Yang Yingliang
2022-10-21  8:05       ` Yang Yingliang via
2022-10-21  8:05       ` Yang Yingliang via Linux-erofs
2022-10-21  8:05       ` Yang Yingliang
2022-10-21  8:05       ` [f2fs-dev] " Yang Yingliang via Linux-f2fs-devel
2022-10-21  8:05       ` [Ocfs2-devel] " Yang Yingliang via Ocfs2-devel
2022-10-21  8:16       ` Greg KH
2022-10-21  8:16         ` Greg KH
2022-10-21  8:16         ` Greg KH
2022-10-21  8:16         ` Greg KH
2022-10-21  8:16         ` [f2fs-dev] " Greg KH
2022-10-21  8:16         ` [Ocfs2-devel] " Greg KH via Ocfs2-devel
2022-10-21  8:18       ` Luben Tuikov
2022-10-21  8:18         ` [Ocfs2-devel] " Luben Tuikov via Ocfs2-devel
2022-10-21  8:18         ` Luben Tuikov
2022-10-21  8:18         ` Luben Tuikov via Linux-erofs
2022-10-21  8:18         ` Luben Tuikov
2022-10-21  8:18         ` [f2fs-dev] " Luben Tuikov via Linux-f2fs-devel
2022-10-21  2:20 ` [PATCH 02/11] kset: add null pointer check in kset_put() Yang Yingliang
2022-10-21  2:20   ` Yang Yingliang
2022-10-21  2:20   ` Yang Yingliang via
2022-10-21  2:20   ` Yang Yingliang via Linux-erofs
2022-10-21  2:20   ` Yang Yingliang
2022-10-21  2:20   ` [f2fs-dev] " Yang Yingliang via Linux-f2fs-devel
2022-10-21  2:20   ` [Ocfs2-devel] " Yang Yingliang via Ocfs2-devel
2022-10-21  2:20 ` [PATCH 03/11] bus: fix possible memory leak in bus_register() Yang Yingliang
2022-10-21  2:20   ` Yang Yingliang
2022-10-21  2:20   ` Yang Yingliang via
2022-10-21  2:20   ` Yang Yingliang via Linux-erofs
2022-10-21  2:20   ` Yang Yingliang
2022-10-21  2:20   ` [f2fs-dev] " Yang Yingliang via Linux-f2fs-devel
2022-10-21  2:20   ` [Ocfs2-devel] " Yang Yingliang via Ocfs2-devel
2022-10-21  2:20 ` Yang Yingliang [this message]
2022-10-21  2:20   ` [PATCH 04/11] kobject: fix possible memory leak in kset_create_and_add() Yang Yingliang
2022-10-21  2:20   ` Yang Yingliang via
2022-10-21  2:20   ` Yang Yingliang via Linux-erofs
2022-10-21  2:20   ` Yang Yingliang
2022-10-21  2:20   ` [f2fs-dev] " Yang Yingliang via Linux-f2fs-devel
2022-10-21  2:20   ` [Ocfs2-devel] " Yang Yingliang via Ocfs2-devel
2022-10-21  2:20 ` [Ocfs2-devel] [PATCH 05/11] class: fix possible memory leak in __class_register() Yang Yingliang via Ocfs2-devel
2022-10-21  2:20   ` Yang Yingliang
2022-10-21  2:20   ` Yang Yingliang via
2022-10-21  2:20   ` Yang Yingliang via Linux-erofs
2022-10-21  2:20   ` Yang Yingliang
2022-10-21  2:20   ` Yang Yingliang
2022-10-21  2:20   ` [f2fs-dev] " Yang Yingliang via Linux-f2fs-devel
2022-10-21  2:20 ` [PATCH 06/11] firmware: qemu_fw_cfg: fix possible memory leak in fw_cfg_build_symlink() Yang Yingliang
2022-10-21  2:20   ` Yang Yingliang
2022-10-21  2:20   ` Yang Yingliang via
2022-10-21  2:20   ` Yang Yingliang via Linux-erofs
2022-10-21  2:20   ` Yang Yingliang
2022-10-21  2:20   ` [f2fs-dev] " Yang Yingliang via Linux-f2fs-devel
2022-10-21  2:20   ` [Ocfs2-devel] " Yang Yingliang via Ocfs2-devel
2022-10-21  2:20 ` [PATCH 07/11] f2fs: fix possible memory leak in f2fs_init_sysfs() Yang Yingliang
2022-10-21  2:20   ` Yang Yingliang
2022-10-21  2:20   ` Yang Yingliang via
2022-10-21  2:20   ` Yang Yingliang via Linux-erofs
2022-10-21  2:20   ` Yang Yingliang
2022-10-21  2:20   ` [f2fs-dev] " Yang Yingliang via Linux-f2fs-devel
2022-10-21  2:20   ` [Ocfs2-devel] " Yang Yingliang via Ocfs2-devel
2022-10-21  2:20 ` [PATCH 08/11] erofs: fix possible memory leak in erofs_init_sysfs() Yang Yingliang
2022-10-21  2:20   ` Yang Yingliang
2022-10-21  2:20   ` Yang Yingliang via
2022-10-21  2:20   ` Yang Yingliang
2022-10-21  2:20   ` Yang Yingliang via Linux-erofs
2022-10-21  2:20   ` [f2fs-dev] " Yang Yingliang via Linux-f2fs-devel
2022-10-21  2:20   ` [Ocfs2-devel] " Yang Yingliang via Ocfs2-devel
2022-10-21  2:21 ` [Ocfs2-devel] [PATCH 09/11] ocfs2: possible memory leak in mlog_sys_init() Yang Yingliang via Ocfs2-devel
2022-10-21  2:21   ` Yang Yingliang
2022-10-21  2:21   ` Yang Yingliang via Linux-erofs
2022-10-21  2:21   ` Yang Yingliang via
2022-10-21  2:21   ` Yang Yingliang
2022-10-21  2:21   ` Yang Yingliang
2022-10-21  2:21   ` [f2fs-dev] " Yang Yingliang via Linux-f2fs-devel
2022-10-21  2:21 ` [PATCH 10/11] drm/amdgpu/discovery: fix possible memory leak Yang Yingliang
2022-10-21  2:21   ` Yang Yingliang
2022-10-21  2:21   ` Yang Yingliang via
2022-10-21  2:21   ` Yang Yingliang via Linux-erofs
2022-10-21  2:21   ` Yang Yingliang
2022-10-21  2:21   ` [f2fs-dev] " Yang Yingliang via Linux-f2fs-devel
2022-10-21  2:21   ` [Ocfs2-devel] " Yang Yingliang via Ocfs2-devel
2022-10-21  2:21 ` [PATCH 11/11] ubifs: Fix memory leak in ubifs_sysfs_init() Yang Yingliang
2022-10-21  2:21   ` Yang Yingliang
2022-10-21  2:21   ` Yang Yingliang via
2022-10-21  2:21   ` Yang Yingliang via Linux-erofs
2022-10-21  2:21   ` Yang Yingliang
2022-10-21  2:21   ` [f2fs-dev] " Yang Yingliang via Linux-f2fs-devel
2022-10-21  2:21   ` [Ocfs2-devel] " Yang Yingliang via Ocfs2-devel
2022-10-21  5:29 ` [PATCH 00/11] fix memory leak while kset_register() fails Luben Tuikov
2022-10-21  5:29   ` [Ocfs2-devel] " Luben Tuikov via Ocfs2-devel
2022-10-21  5:29   ` [f2fs-dev] " Luben Tuikov via Linux-f2fs-devel
2022-10-21  5:29   ` Luben Tuikov via Linux-erofs
2022-10-21  5:29   ` Luben Tuikov
2022-10-21  5:29   ` Luben Tuikov
2022-10-21  5:37   ` Greg KH
2022-10-21  5:37     ` Greg KH
2022-10-21  5:37     ` Greg KH
2022-10-21  5:37     ` Greg KH
2022-10-21  5:37     ` [f2fs-dev] " Greg KH
2022-10-21  5:37     ` [Ocfs2-devel] " Greg KH via Ocfs2-devel
2022-10-21  7:55     ` Luben Tuikov
2022-10-21  7:55       ` [Ocfs2-devel] " Luben Tuikov via Ocfs2-devel
2022-10-21  7:55       ` Luben Tuikov
2022-10-21  7:55       ` Luben Tuikov via Linux-erofs
2022-10-21  7:55       ` Luben Tuikov
2022-10-21  8:18       ` Greg KH
2022-10-21  8:18         ` Greg KH
2022-10-21  8:18         ` Greg KH
2022-10-21  8:18         ` Greg KH
2022-10-21  8:18         ` [f2fs-dev] " Greg KH
2022-10-21  8:18         ` [Ocfs2-devel] " Greg KH via Ocfs2-devel
2022-10-21  8:24         ` Luben Tuikov
2022-10-21  8:24           ` [Ocfs2-devel] " Luben Tuikov via Ocfs2-devel
2022-10-21  8:24           ` [f2fs-dev] " Luben Tuikov via Linux-f2fs-devel
2022-10-21  8:24           ` Luben Tuikov
2022-10-21  8:24           ` Luben Tuikov
2022-10-21  8:24           ` Luben Tuikov via Linux-erofs
2022-10-21  8:41           ` Luben Tuikov
2022-10-21  8:41             ` [Ocfs2-devel] " Luben Tuikov via Ocfs2-devel
2022-10-21  8:41             ` [f2fs-dev] " Luben Tuikov via Linux-f2fs-devel
2022-10-21  8:41             ` Luben Tuikov via Linux-erofs
2022-10-21  8:41             ` Luben Tuikov
2022-10-21  8:41             ` Luben Tuikov
2022-10-21  9:23             ` [Ocfs2-devel] " Yang Yingliang via Ocfs2-devel
2022-10-21  9:23               ` Yang Yingliang
2022-10-21  9:23               ` Yang Yingliang via
2022-10-21  9:23               ` Yang Yingliang
2022-10-21  9:23               ` Yang Yingliang via Linux-erofs
2022-10-21  9:23               ` Yang Yingliang
2022-10-21  9:23               ` [f2fs-dev] " Yang Yingliang via Linux-f2fs-devel
2022-10-21  8:24     ` Yang Yingliang
2022-10-21  8:24       ` Yang Yingliang
2022-10-21  8:24       ` Yang Yingliang via
2022-10-21  8:24       ` Yang Yingliang
2022-10-21  8:24       ` Yang Yingliang via Linux-erofs
2022-10-21  8:24       ` [f2fs-dev] " Yang Yingliang via Linux-f2fs-devel
2022-10-21  8:24       ` [Ocfs2-devel] " Yang Yingliang via Ocfs2-devel
2022-10-21  8:36       ` Greg KH
2022-10-21  8:36         ` Greg KH
2022-10-21  8:36         ` Greg KH
2022-10-21  8:36         ` Greg KH
2022-10-21  8:36         ` [f2fs-dev] " Greg KH
2022-10-21  8:36         ` [Ocfs2-devel] " Greg KH via Ocfs2-devel
2022-10-21  8:52         ` Luben Tuikov
2022-10-21  8:52           ` [Ocfs2-devel] " Luben Tuikov via Ocfs2-devel
2022-10-21  8:52           ` Luben Tuikov
2022-10-21  8:52           ` Luben Tuikov via Linux-erofs
2022-10-21  8:52           ` Luben Tuikov
2022-10-21  8:52           ` [f2fs-dev] " Luben Tuikov via Linux-f2fs-devel
2022-10-21  8:59         ` Yang Yingliang
2022-10-21  8:59           ` Yang Yingliang
2022-10-21  8:59           ` Yang Yingliang via
2022-10-21  8:59           ` [f2fs-dev] " Yang Yingliang via Linux-f2fs-devel
2022-10-21  8:59           ` Yang Yingliang via Linux-erofs
2022-10-21  8:59           ` Yang Yingliang
2022-10-21  8:59           ` [Ocfs2-devel] " Yang Yingliang via Ocfs2-devel
2022-10-21  9:08           ` Luben Tuikov
2022-10-21  9:08             ` [Ocfs2-devel] " Luben Tuikov via Ocfs2-devel
2022-10-21  9:08             ` Luben Tuikov
2022-10-21  9:08             ` Luben Tuikov via Linux-erofs
2022-10-21  9:08             ` Luben Tuikov
2022-10-21  9:08             ` [f2fs-dev] " Luben Tuikov via Linux-f2fs-devel
2022-10-21  9:56             ` Yang Yingliang
2022-10-21  9:56               ` Yang Yingliang
2022-10-21  9:56               ` Yang Yingliang via
2022-10-21  9:56               ` Yang Yingliang via Linux-erofs
2022-10-21  9:56               ` Yang Yingliang
2022-10-21  9:56               ` [f2fs-dev] " Yang Yingliang via Linux-f2fs-devel
2022-10-21  9:56               ` [Ocfs2-devel] " Yang Yingliang via Ocfs2-devel
2022-10-21 23:45               ` Luben Tuikov
2022-10-21 23:45                 ` Luben Tuikov
2022-10-21 23:45                 ` Luben Tuikov via Linux-erofs
2022-10-21 23:45                 ` Luben Tuikov
2022-10-21 23:45                 ` [f2fs-dev] " Luben Tuikov via Linux-f2fs-devel
2022-10-21 23:45                 ` [Ocfs2-devel] " Luben Tuikov via Ocfs2-devel
2022-10-21  9:12         ` Yang Yingliang
2022-10-21  9:12           ` Yang Yingliang
2022-10-21  9:12           ` Yang Yingliang via
2022-10-21  9:12           ` [Ocfs2-devel] " Yang Yingliang via Ocfs2-devel
2022-10-21  9:12           ` Yang Yingliang
2022-10-21  9:12           ` Yang Yingliang via Linux-erofs
2022-10-21  9:12           ` [f2fs-dev] " Yang Yingliang via Linux-f2fs-devel
2022-10-21 23:48           ` Luben Tuikov
2022-10-21 23:48             ` [f2fs-dev] " Luben Tuikov via Linux-f2fs-devel
2022-10-21 23:48             ` Luben Tuikov via Linux-erofs
2022-10-21 23:48             ` Luben Tuikov
2022-10-21 23:48             ` [Ocfs2-devel] " Luben Tuikov via Ocfs2-devel
2022-10-21 23:48             ` Luben Tuikov
2022-10-21  7:25   ` Yang Yingliang
2022-10-21  7:25     ` Yang Yingliang
2022-10-21  7:25     ` Yang Yingliang via
2022-10-21  7:25     ` Yang Yingliang
2022-10-21  7:25     ` Yang Yingliang via Linux-erofs
2022-10-21  7:25     ` [f2fs-dev] " Yang Yingliang via Linux-f2fs-devel
2022-10-21  7:25     ` [Ocfs2-devel] " Yang Yingliang via Ocfs2-devel

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=20221021022102.2231464-5-yangyingliang@huawei.com \
    --to=yangyingliang@huawei.com \
    --cc=akpm@linux-foundation.org \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=chao@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hsiangkao@linux.alibaba.com \
    --cc=huangjianan@oppo.com \
    --cc=jaegeuk@kernel.org \
    --cc=jlbec@evilplan.org \
    --cc=joseph.qi@linux.alibaba.com \
    --cc=linux-erofs@lists.ozlabs.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=liushixin2@huawei.com \
    --cc=luben.tuikov@amd.com \
    --cc=mark@fasheh.com \
    --cc=mst@redhat.com \
    --cc=ocfs2-devel@oss.oracle.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rafael@kernel.org \
    --cc=richard@nod.at \
    --cc=somlo@cmu.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.