From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: "Uwe Kleine-König" <uwe@kleine-koenig.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Sasha Levin" <sashal@kernel.org>
Subject: [PATCH 5.10.y 4/7] driver core: platform: Emit a warning if a remove callback returned non-zero
Date: Wed, 9 Sep 2026 07:18:02 -0400 [thread overview]
Message-ID: <20260909111805.1804682-4-sashal@kernel.org> (raw)
In-Reply-To: <20260909111805.1804682-1-sashal@kernel.org>
From: Uwe Kleine-König <uwe@kleine-koenig.org>
[ Upstream commit e5e1c209788138f33ca6558bf9f572f6904f486d ]
The driver core ignores the return value of a bus' remove callback. However
a driver returning an error code is a hint that there is a problem,
probably a driver author who expects that returning e.g. -EBUSY has any
effect.
The right thing to do would be to make struct platform_driver::remove()
return void. With the immense number of platform drivers this is however a
big quest and I hope to prevent at least a few new drivers that return an
error code here.
Signed-off-by: Uwe Kleine-König <uwe@kleine-koenig.org>
Link: https://lore.kernel.org/r/20210207211537.19992-1-uwe@kleine-koenig.org
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Stable-dep-of: c57cb36f76eb ("power: supply: charger-manager: register regulators before exposing sysfs")
Signed-off-by: Sasha Levin <sashal@kernel.org>
---
drivers/base/platform.c | 11 +++++++----
1 file changed, 7 insertions(+), 4 deletions(-)
diff --git a/drivers/base/platform.c b/drivers/base/platform.c
index 90166535a5c05..d0b15cbab0ff0 100644
--- a/drivers/base/platform.c
+++ b/drivers/base/platform.c
@@ -1305,13 +1305,16 @@ static int platform_remove(struct device *_dev)
{
struct platform_driver *drv = to_platform_driver(_dev->driver);
struct platform_device *dev = to_platform_device(_dev);
- int ret = 0;
- if (drv->remove)
- ret = drv->remove(dev);
+ if (drv->remove) {
+ int ret = drv->remove(dev);
+
+ if (ret)
+ dev_warn(_dev, "remove callback returned a non-zero value. This will be ignored.\n");
+ }
dev_pm_domain_detach(_dev, true);
- return ret;
+ return 0;
}
static void platform_shutdown(struct device *_dev)
--
2.53.0
next prev parent reply other threads:[~2026-09-09 11:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 14:38 FAILED: patch "[PATCH] power: supply: charger-manager: register regulators before" failed to apply to 5.10-stable tree gregkh
2026-09-09 11:17 ` [PATCH 5.10.y 1/7] driver core: platform: reorder functions Sasha Levin
2026-09-09 11:18 ` [PATCH 5.10.y 2/7] driver core: platform: change logic implementing platform_driver_probe Sasha Levin
2026-09-09 11:18 ` [PATCH 5.10.y 3/7] driver core: platform: use bus_type functions Sasha Levin
2026-09-09 11:18 ` Sasha Levin [this message]
2026-09-09 11:18 ` [PATCH 5.10.y 5/7] platform: Provide a remove callback that returns no value Sasha Levin
2026-09-09 11:18 ` [PATCH 5.10.y 6/7] power: supply: charger-manager: Convert to platform remove callback returning void Sasha Levin
2026-09-09 11:18 ` [PATCH 5.10.y 7/7] power: supply: charger-manager: register regulators before exposing sysfs Sasha Levin
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=20260909111805.1804682-4-sashal@kernel.org \
--to=sashal@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=stable@vger.kernel.org \
--cc=uwe@kleine-koenig.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