From: Zijun Hu <zijun_hu@icloud.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>
Cc: linux-kernel@vger.kernel.org, Zijun Hu <quic_zijuhu@quicinc.com>
Subject: Re: [PATCH v2] driver core: bus: Remove an impossible error handling path in bus_add_driver()
Date: Tue, 17 Sep 2024 14:53:32 +0800 [thread overview]
Message-ID: <420b202e-e094-4e82-bf77-dd1c62119aa7@icloud.com> (raw)
In-Reply-To: <20240917-bus_add_driver_fix-v2-1-a94026443444@quicinc.com>
On 2024/9/17 14:49, Zijun Hu wrote:
> From: Zijun Hu <quic_zijuhu@quicinc.com>
>
> For the following function call chain:
> API driver_register() -> bus_add_driver() -> driver_attach()
>
> There is an error handling path for driver_attach() returning non-zero
> or failure in bus_add_driver(), remove it with below reasons:
>
> - It is impossible for driver_attach() to have failure in bus_add_driver()
> For int driver_attach(const struct device_driver *drv), the only factor
> which makes it failed is that bus_to_subsys(@drv->bus) is NULL, but
> the factor has been excluded by bus_add_driver() before calling it.
>
> - driver_attach() is irrelevant with driver_register(), so the former's
> result should not also have an impact on the later.
>
> Signed-off-by: Zijun Hu <quic_zijuhu@quicinc.com>
> ---
> Changes in v2:
> - Remove the error handling path instead of WARN_ON() it.
> - Correct title and commit message
> - Link to v1: https://lore.kernel.org/r/20240915-bus_add_driver_fix-v1-1-ce5cf1f66601@quicinc.com
> ---
> drivers/base/bus.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/base/bus.c b/drivers/base/bus.c
> index 657c93c38b0d..54ff92aece92 100644
> --- a/drivers/base/bus.c
> +++ b/drivers/base/bus.c
> @@ -674,7 +674,8 @@ int bus_add_driver(struct device_driver *drv)
> if (sp->drivers_autoprobe) {
> error = driver_attach(drv);
> if (error)
> - goto out_del_list;
> + pr_warn("%s: failed to attach driver '%s' to bus '%s'\n",
> + __func__, drv->name, sp->bus->name);
driver_attach() has __must_check attribute and this error may be
inconsequential for driver_register(), so give pr_warn() here
> }
> error = module_add_driver(drv->owner, drv);
> if (error) {
> @@ -708,7 +709,6 @@ int bus_add_driver(struct device_driver *drv)
>
> out_detach:
> driver_detach(drv);
> -out_del_list:
> klist_del(&priv->knode_bus);
> out_unregister:
> kobject_put(&priv->kobj);
>
> ---
> base-commit: 6a36d828bdef0e02b1e6c12e2160f5b83be6aab5
> change-id: 20240915-bus_add_driver_fix-f54841e6a69a
>
> Best regards,
next prev parent reply other threads:[~2024-09-17 6:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-17 6:49 Zijun Hu
2024-09-17 6:53 ` Zijun Hu [this message]
2024-10-13 15:02 ` Greg Kroah-Hartman
2024-10-13 15:46 ` Zijun Hu
2024-10-13 16:00 ` Greg Kroah-Hartman
2024-10-13 16:13 ` Zijun Hu
2024-10-13 16:24 ` Greg Kroah-Hartman
2024-10-13 16:35 ` Zijun Hu
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=420b202e-e094-4e82-bf77-dd1c62119aa7@icloud.com \
--to=zijun_hu@icloud.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_zijuhu@quicinc.com \
--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
all inboxes | Powered by JetHome®