From: Maxime Ripard <mripard@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>
Cc: Brendan Higgins <brendan.higgins@linux.dev>,
David Gow <davidgow@google.com>,
linux-kselftest@vger.kernel.org, kunit-dev@googlegroups.com,
linux-kernel@vger.kernel.org, Maxime Ripard <mripard@kernel.org>,
Maxime Ripard <mripard@kernel.org>
Subject: [PATCH v2 3/3] drivers: base: Free devm resources when unregistering a device
Date: Wed, 28 Jun 2023 11:49:23 +0200 [thread overview]
Message-ID: <20230329-kunit-devm-inconsistencies-test-v2-3-19feb71e864b@kernel.org> (raw)
In-Reply-To: <20230329-kunit-devm-inconsistencies-test-v2-0-19feb71e864b@kernel.org>
From: David Gow <davidgow@google.com>
In the current code, devres_release_all() only gets called if the device
has a bus and has been probed.
This leads to issues when using bus-less or driver-less devices where
the device might never get freed if a managed resource holds a reference
to the device. This is happening in the DRM framework for example.
We should thus call devres_release_all() in the device_del() function to
make sure that the device-managed actions are properly executed when the
device is unregistered, even if it has neither a bus nor a driver.
This is effectively the same change than commit 2f8d16a996da ("devres:
release resources on device_del()") that got reverted by commit
a525a3ddeaca ("driver core: free devres in device_release") over
use-after-free concerns.
It's not clear whether those concerns are legitimate though, but I would
expect drivers not to register new resources in their device-managed
actions.
Fixes: a525a3ddeaca ("driver core: free devres in device_release")
Signed-off-by: Maxime Ripard <mripard@kernel.org>
---
drivers/base/core.c | 11 +++++++++++
drivers/base/test/platform-device-test.c | 2 --
drivers/base/test/root-device-test.c | 2 --
3 files changed, 11 insertions(+), 4 deletions(-)
diff --git a/drivers/base/core.c b/drivers/base/core.c
index 3dff5037943e..6ceaf50f5a67 100644
--- a/drivers/base/core.c
+++ b/drivers/base/core.c
@@ -3817,6 +3817,17 @@ void device_del(struct device *dev)
device_platform_notify_remove(dev);
device_links_purge(dev);
+ /*
+ * If a device does not have a driver attached, we need to clean
+ * up any managed resources. We do this in device_release(), but
+ * it's never called (and we leak the device) if a managed
+ * resource holds a reference to the device. So release all
+ * managed resources here, like we do in driver_detach(). We
+ * still need to do so again in device_release() in case someone
+ * adds a new resource after this point, though.
+ */
+ devres_release_all(dev);
+
bus_notify(dev, BUS_NOTIFY_REMOVED_DEVICE);
kobject_uevent(&dev->kobj, KOBJ_REMOVE);
glue_dir = get_glue_dir(dev);
diff --git a/drivers/base/test/platform-device-test.c b/drivers/base/test/platform-device-test.c
index b6ebf1dcdffb..1ae5ce8bd366 100644
--- a/drivers/base/test/platform-device-test.c
+++ b/drivers/base/test/platform-device-test.c
@@ -87,8 +87,6 @@ static void platform_device_devm_register_get_unregister_with_devm_test(struct k
struct test_priv *priv = test->priv;
int ret;
- kunit_skip(test, "This needs to be fixed in the core.");
-
pdev = platform_device_alloc(DEVICE_NAME, PLATFORM_DEVID_NONE);
KUNIT_ASSERT_NOT_ERR_OR_NULL(test, pdev);
diff --git a/drivers/base/test/root-device-test.c b/drivers/base/test/root-device-test.c
index 9a3e6cccae13..780d07455f57 100644
--- a/drivers/base/test/root-device-test.c
+++ b/drivers/base/test/root-device-test.c
@@ -78,8 +78,6 @@ static void root_device_devm_register_get_unregister_with_devm_test(struct kunit
struct test_priv *priv = test->priv;
int ret;
- kunit_skip(test, "This needs to be fixed in the core.");
-
priv->dev = root_device_register(DEVICE_NAME);
KUNIT_ASSERT_NOT_ERR_OR_NULL(test, priv->dev);
--
2.40.0
next prev parent reply other threads:[~2023-06-28 9:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 9:49 [PATCH v2 0/3] drivers: base: Add tests showing devm handling inconsistencies Maxime Ripard
2023-06-28 9:49 ` [PATCH v2 1/3] drivers: base: Add basic devm tests for root devices Maxime Ripard
2023-07-19 9:13 ` David Gow
2023-07-20 11:29 ` Maxime Ripard
2023-06-28 9:49 ` [PATCH v2 2/3] drivers: base: Add basic devm tests for platform devices Maxime Ripard
2023-07-19 9:13 ` David Gow
2023-07-20 11:40 ` Maxime Ripard
2023-06-28 9:49 ` Maxime Ripard [this message]
2023-07-19 9:13 ` [PATCH v2 3/3] drivers: base: Free devm resources when unregistering a device David Gow
2023-07-20 11:57 ` Maxime Ripard
2023-07-18 14:35 ` [PATCH v2 0/3] drivers: base: Add tests showing devm handling inconsistencies Maxime Ripard
2023-07-19 9:13 ` David Gow
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=20230329-kunit-devm-inconsistencies-test-v2-3-19feb71e864b@kernel.org \
--to=mripard@kernel.org \
--cc=brendan.higgins@linux.dev \
--cc=davidgow@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=rafael@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox