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 v2] kset: fix memory leak when kset_register() returns error
Date: Mon, 24 Oct 2022 20:19:10 +0800 [thread overview]
Message-ID: <20221024121910.1169801-1-yangyingliang@huawei.com> (raw)
Inject fault while loading module, kset_register() may fail.
If it fails, the name allocated by kobject_set_name() which
is called before kset_register() is leaked, because refcount
of kobject is hold in kset_init().
As a kset may be embedded in a larger structure which needs
be freed in release() function or error path in callers, we
can not call kset_put() in kset_register(), or it will cause
double free, so just call kfree_const() to free the name and
set it to NULL.
With this fix, the callers don't need to care about the name
freeing and call an extra kset_put() if kset_register() fails.
Suggested-by: Luben Tuikov <luben.tuikov@amd.com>
Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
---
v1 -> v2:
Free name inside of kset_register() instead of calling kset_put()
in drivers.
---
lib/kobject.c | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/lib/kobject.c b/lib/kobject.c
index a0b2dbfcfa23..3409a89c81e5 100644
--- a/lib/kobject.c
+++ b/lib/kobject.c
@@ -834,6 +834,9 @@ EXPORT_SYMBOL_GPL(kobj_sysfs_ops);
/**
* kset_register() - Initialize and add a kset.
* @k: kset.
+ *
+ * NOTE: On error, the kset.kobj.name allocated by() kobj_set_name()
+ * which is called before kset_register() in caller need be freed.
*/
int kset_register(struct kset *k)
{
@@ -844,8 +847,11 @@ int kset_register(struct kset *k)
kset_init(k);
err = kobject_add_internal(&k->kobj);
- if (err)
+ if (err) {
+ kfree_const(k->kobj.name);
+ k->kobj.name = NULL;
return err;
+ }
kobject_uevent(&k->kobj, KOBJ_ADD);
return 0;
}
--
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 v2] kset: fix memory leak when kset_register() returns error
Date: Mon, 24 Oct 2022 20:19:10 +0800 [thread overview]
Message-ID: <20221024121910.1169801-1-yangyingliang@huawei.com> (raw)
Inject fault while loading module, kset_register() may fail.
If it fails, the name allocated by kobject_set_name() which
is called before kset_register() is leaked, because refcount
of kobject is hold in kset_init().
As a kset may be embedded in a larger structure which needs
be freed in release() function or error path in callers, we
can not call kset_put() in kset_register(), or it will cause
double free, so just call kfree_const() to free the name and
set it to NULL.
With this fix, the callers don't need to care about the name
freeing and call an extra kset_put() if kset_register() fails.
Suggested-by: Luben Tuikov <luben.tuikov@amd.com>
Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
---
v1 -> v2:
Free name inside of kset_register() instead of calling kset_put()
in drivers.
---
lib/kobject.c | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/lib/kobject.c b/lib/kobject.c
index a0b2dbfcfa23..3409a89c81e5 100644
--- a/lib/kobject.c
+++ b/lib/kobject.c
@@ -834,6 +834,9 @@ EXPORT_SYMBOL_GPL(kobj_sysfs_ops);
/**
* kset_register() - Initialize and add a kset.
* @k: kset.
+ *
+ * NOTE: On error, the kset.kobj.name allocated by() kobj_set_name()
+ * which is called before kset_register() in caller need be freed.
*/
int kset_register(struct kset *k)
{
@@ -844,8 +847,11 @@ int kset_register(struct kset *k)
kset_init(k);
err = kobject_add_internal(&k->kobj);
- if (err)
+ if (err) {
+ kfree_const(k->kobj.name);
+ k->kobj.name = NULL;
return err;
+ }
kobject_uevent(&k->kobj, KOBJ_ADD);
return 0;
}
--
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 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 v2] kset: fix memory leak when kset_register() returns error
Date: Mon, 24 Oct 2022 20:19:10 +0800 [thread overview]
Message-ID: <20221024121910.1169801-1-yangyingliang@huawei.com> (raw)
Inject fault while loading module, kset_register() may fail.
If it fails, the name allocated by kobject_set_name() which
is called before kset_register() is leaked, because refcount
of kobject is hold in kset_init().
As a kset may be embedded in a larger structure which needs
be freed in release() function or error path in callers, we
can not call kset_put() in kset_register(), or it will cause
double free, so just call kfree_const() to free the name and
set it to NULL.
With this fix, the callers don't need to care about the name
freeing and call an extra kset_put() if kset_register() fails.
Suggested-by: Luben Tuikov <luben.tuikov@amd.com>
Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
---
v1 -> v2:
Free name inside of kset_register() instead of calling kset_put()
in drivers.
---
lib/kobject.c | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/lib/kobject.c b/lib/kobject.c
index a0b2dbfcfa23..3409a89c81e5 100644
--- a/lib/kobject.c
+++ b/lib/kobject.c
@@ -834,6 +834,9 @@ EXPORT_SYMBOL_GPL(kobj_sysfs_ops);
/**
* kset_register() - Initialize and add a kset.
* @k: kset.
+ *
+ * NOTE: On error, the kset.kobj.name allocated by() kobj_set_name()
+ * which is called before kset_register() in caller need be freed.
*/
int kset_register(struct kset *k)
{
@@ -844,8 +847,11 @@ int kset_register(struct kset *k)
kset_init(k);
err = kobject_add_internal(&k->kobj);
- if (err)
+ if (err) {
+ kfree_const(k->kobj.name);
+ k->kobj.name = NULL;
return err;
+ }
kobject_uevent(&k->kobj, KOBJ_ADD);
return 0;
}
--
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: <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 v2] kset: fix memory leak when kset_register() returns error
Date: Mon, 24 Oct 2022 20:19:10 +0800 [thread overview]
Message-ID: <20221024121910.1169801-1-yangyingliang@huawei.com> (raw)
Inject fault while loading module, kset_register() may fail.
If it fails, the name allocated by kobject_set_name() which
is called before kset_register() is leaked, because refcount
of kobject is hold in kset_init().
As a kset may be embedded in a larger structure which needs
be freed in release() function or error path in callers, we
can not call kset_put() in kset_register(), or it will cause
double free, so just call kfree_const() to free the name and
set it to NULL.
With this fix, the callers don't need to care about the name
freeing and call an extra kset_put() if kset_register() fails.
Suggested-by: Luben Tuikov <luben.tuikov@amd.com>
Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
---
v1 -> v2:
Free name inside of kset_register() instead of calling kset_put()
in drivers.
---
lib/kobject.c | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/lib/kobject.c b/lib/kobject.c
index a0b2dbfcfa23..3409a89c81e5 100644
--- a/lib/kobject.c
+++ b/lib/kobject.c
@@ -834,6 +834,9 @@ EXPORT_SYMBOL_GPL(kobj_sysfs_ops);
/**
* kset_register() - Initialize and add a kset.
* @k: kset.
+ *
+ * NOTE: On error, the kset.kobj.name allocated by() kobj_set_name()
+ * which is called before kset_register() in caller need be freed.
*/
int kset_register(struct kset *k)
{
@@ -844,8 +847,11 @@ int kset_register(struct kset *k)
kset_init(k);
err = kobject_add_internal(&k->kobj);
- if (err)
+ if (err) {
+ kfree_const(k->kobj.name);
+ k->kobj.name = NULL;
return err;
+ }
kobject_uevent(&k->kobj, KOBJ_ADD);
return 0;
}
--
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 <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 v2] kset: fix memory leak when kset_register() returns error
Date: Mon, 24 Oct 2022 20:19:10 +0800 [thread overview]
Message-ID: <20221024121910.1169801-1-yangyingliang@huawei.com> (raw)
Inject fault while loading module, kset_register() may fail.
If it fails, the name allocated by kobject_set_name() which
is called before kset_register() is leaked, because refcount
of kobject is hold in kset_init().
As a kset may be embedded in a larger structure which needs
be freed in release() function or error path in callers, we
can not call kset_put() in kset_register(), or it will cause
double free, so just call kfree_const() to free the name and
set it to NULL.
With this fix, the callers don't need to care about the name
freeing and call an extra kset_put() if kset_register() fails.
Suggested-by: Luben Tuikov <luben.tuikov@amd.com>
Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
---
v1 -> v2:
Free name inside of kset_register() instead of calling kset_put()
in drivers.
---
lib/kobject.c | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/lib/kobject.c b/lib/kobject.c
index a0b2dbfcfa23..3409a89c81e5 100644
--- a/lib/kobject.c
+++ b/lib/kobject.c
@@ -834,6 +834,9 @@ EXPORT_SYMBOL_GPL(kobj_sysfs_ops);
/**
* kset_register() - Initialize and add a kset.
* @k: kset.
+ *
+ * NOTE: On error, the kset.kobj.name allocated by() kobj_set_name()
+ * which is called before kset_register() in caller need be freed.
*/
int kset_register(struct kset *k)
{
@@ -844,8 +847,11 @@ int kset_register(struct kset *k)
kset_init(k);
err = kobject_add_internal(&k->kobj);
- if (err)
+ if (err) {
+ kfree_const(k->kobj.name);
+ k->kobj.name = NULL;
return err;
+ }
kobject_uevent(&k->kobj, KOBJ_ADD);
return 0;
}
--
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 v2] kset: fix memory leak when kset_register() returns error
Date: Mon, 24 Oct 2022 20:19:10 +0800 [thread overview]
Message-ID: <20221024121910.1169801-1-yangyingliang@huawei.com> (raw)
Inject fault while loading module, kset_register() may fail.
If it fails, the name allocated by kobject_set_name() which
is called before kset_register() is leaked, because refcount
of kobject is hold in kset_init().
As a kset may be embedded in a larger structure which needs
be freed in release() function or error path in callers, we
can not call kset_put() in kset_register(), or it will cause
double free, so just call kfree_const() to free the name and
set it to NULL.
With this fix, the callers don't need to care about the name
freeing and call an extra kset_put() if kset_register() fails.
Suggested-by: Luben Tuikov <luben.tuikov@amd.com>
Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
---
v1 -> v2:
Free name inside of kset_register() instead of calling kset_put()
in drivers.
---
lib/kobject.c | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/lib/kobject.c b/lib/kobject.c
index a0b2dbfcfa23..3409a89c81e5 100644
--- a/lib/kobject.c
+++ b/lib/kobject.c
@@ -834,6 +834,9 @@ EXPORT_SYMBOL_GPL(kobj_sysfs_ops);
/**
* kset_register() - Initialize and add a kset.
* @k: kset.
+ *
+ * NOTE: On error, the kset.kobj.name allocated by() kobj_set_name()
+ * which is called before kset_register() in caller need be freed.
*/
int kset_register(struct kset *k)
{
@@ -844,8 +847,11 @@ int kset_register(struct kset *k)
kset_init(k);
err = kobject_add_internal(&k->kobj);
- if (err)
+ if (err) {
+ kfree_const(k->kobj.name);
+ k->kobj.name = NULL;
return err;
+ }
kobject_uevent(&k->kobj, KOBJ_ADD);
return 0;
}
--
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: <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 v2] kset: fix memory leak when kset_register() returns error
Date: Mon, 24 Oct 2022 20:19:10 +0800 [thread overview]
Message-ID: <20221024121910.1169801-1-yangyingliang@huawei.com> (raw)
Inject fault while loading module, kset_register() may fail.
If it fails, the name allocated by kobject_set_name() which
is called before kset_register() is leaked, because refcount
of kobject is hold in kset_init().
As a kset may be embedded in a larger structure which needs
be freed in release() function or error path in callers, we
can not call kset_put() in kset_register(), or it will cause
double free, so just call kfree_const() to free the name and
set it to NULL.
With this fix, the callers don't need to care about the name
freeing and call an extra kset_put() if kset_register() fails.
Suggested-by: Luben Tuikov <luben.tuikov@amd.com>
Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
---
v1 -> v2:
Free name inside of kset_register() instead of calling kset_put()
in drivers.
---
lib/kobject.c | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/lib/kobject.c b/lib/kobject.c
index a0b2dbfcfa23..3409a89c81e5 100644
--- a/lib/kobject.c
+++ b/lib/kobject.c
@@ -834,6 +834,9 @@ EXPORT_SYMBOL_GPL(kobj_sysfs_ops);
/**
* kset_register() - Initialize and add a kset.
* @k: kset.
+ *
+ * NOTE: On error, the kset.kobj.name allocated by() kobj_set_name()
+ * which is called before kset_register() in caller need be freed.
*/
int kset_register(struct kset *k)
{
@@ -844,8 +847,11 @@ int kset_register(struct kset *k)
kset_init(k);
err = kobject_add_internal(&k->kobj);
- if (err)
+ if (err) {
+ kfree_const(k->kobj.name);
+ k->kobj.name = NULL;
return err;
+ }
kobject_uevent(&k->kobj, KOBJ_ADD);
return 0;
}
--
2.25.1
next reply other threads:[~2022-10-24 12:20 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 12:19 Yang Yingliang via Ocfs2-devel [this message]
2022-10-24 12:19 ` [PATCH v2] kset: fix memory leak when kset_register() returns error Yang Yingliang
2022-10-24 12:19 ` Yang Yingliang
2022-10-24 12:19 ` Yang Yingliang via
2022-10-24 12:19 ` Yang Yingliang
2022-10-24 12:19 ` Yang Yingliang via Linux-erofs
2022-10-24 12:19 ` [f2fs-dev] " Yang Yingliang via Linux-f2fs-devel
2022-10-24 13:52 ` [Ocfs2-devel] " Greg KH via Ocfs2-devel
2022-10-24 13:52 ` Greg KH
2022-10-24 13:52 ` Greg KH
2022-10-24 13:52 ` Greg KH
2022-10-24 13:52 ` Greg KH
2022-10-24 13:52 ` [f2fs-dev] " Greg KH
2022-10-24 14:39 ` [Ocfs2-devel] " Yang Yingliang via Ocfs2-devel
2022-10-24 14:39 ` Yang Yingliang
2022-10-24 14:39 ` Yang Yingliang via
2022-10-24 14:39 ` Yang Yingliang
2022-10-24 14:39 ` Yang Yingliang via Linux-erofs
2022-10-24 14:39 ` Yang Yingliang
2022-10-24 14:39 ` [f2fs-dev] " Yang Yingliang via Linux-f2fs-devel
2022-10-24 14:53 ` [Ocfs2-devel] " Greg KH via Ocfs2-devel
2022-10-24 14:53 ` Greg KH
2022-10-24 14:53 ` Greg KH
2022-10-24 14:53 ` Greg KH
2022-10-24 14:53 ` Greg KH
2022-10-24 14:53 ` [f2fs-dev] " Greg KH
2022-10-24 15:10 ` [Ocfs2-devel] " Yang Yingliang via Ocfs2-devel
2022-10-24 15:10 ` Yang Yingliang
2022-10-24 15:10 ` Yang Yingliang via
2022-10-24 15:10 ` Yang Yingliang
2022-10-24 15:10 ` Yang Yingliang
2022-10-24 15:10 ` Yang Yingliang via Linux-erofs
2022-10-24 15:10 ` [f2fs-dev] " Yang Yingliang via Linux-f2fs-devel
2022-10-24 21:06 ` [Ocfs2-devel] " Luben Tuikov via Ocfs2-devel
2022-10-24 21:06 ` [f2fs-dev] " Luben Tuikov via Linux-f2fs-devel
2022-10-24 21:06 ` Luben Tuikov
2022-10-24 21:06 ` Luben Tuikov via Linux-erofs
2022-10-24 21:06 ` Luben Tuikov
2022-10-24 21:06 ` Luben Tuikov
2022-10-24 21:25 ` Luben Tuikov
2022-10-24 21:25 ` [f2fs-dev] " Luben Tuikov via Linux-f2fs-devel
2022-10-24 21:25 ` Luben Tuikov
2022-10-24 21:25 ` Luben Tuikov via Linux-erofs
2022-10-24 21:25 ` Luben Tuikov
2022-10-24 21:25 ` [Ocfs2-devel] " Luben Tuikov via Ocfs2-devel
2022-10-25 2:16 ` Yang Yingliang
2022-10-25 2:16 ` Yang Yingliang
2022-10-25 2:16 ` Yang Yingliang via
2022-10-25 2:16 ` Yang Yingliang
2022-10-25 2:16 ` Yang Yingliang via Linux-erofs
2022-10-25 2:16 ` [f2fs-dev] " Yang Yingliang via Linux-f2fs-devel
2022-10-25 2:16 ` [Ocfs2-devel] " Yang Yingliang via Ocfs2-devel
2022-10-25 2:53 ` Luben Tuikov
2022-10-25 2:53 ` Luben Tuikov via Linux-erofs
2022-10-25 2:53 ` Luben Tuikov
2022-10-25 2:53 ` [f2fs-dev] " Luben Tuikov via Linux-f2fs-devel
2022-10-25 2:53 ` Luben Tuikov
2022-10-25 2:53 ` [Ocfs2-devel] " Luben Tuikov 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=20221024121910.1169801-1-yangyingliang@huawei.com \
--to=ocfs2-devel@oss.oracle.com \
--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=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=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rafael@kernel.org \
--cc=richard@nod.at \
--cc=somlo@cmu.edu \
--cc=yangyingliang@huawei.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 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.