From: "Danilo Krummrich" <dakr@kernel.org>
To: "Johan Hovold" <johan@kernel.org>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Rafael J . Wysocki" <rafael@kernel.org>,
<driver-core@lists.linux.dev>, <linux-kernel@vger.kernel.org>,
<stable@vger.kernel.org>
Subject: Re: [PATCH] driver core: faux: fix root device registration
Date: Fri, 24 Apr 2026 13:42:12 +0200 [thread overview]
Message-ID: <DI1CW4GWGUD6.2K7VZG165WJP8@kernel.org> (raw)
In-Reply-To: <20260424102231.2615557-1-johan@kernel.org>
On Fri Apr 24, 2026 at 12:22 PM CEST, Johan Hovold wrote:
> diff --git a/drivers/base/faux.c b/drivers/base/faux.c
> index fb3e42f21362..402ed119dfdf 100644
> --- a/drivers/base/faux.c
> +++ b/drivers/base/faux.c
> @@ -133,6 +133,9 @@ struct faux_device *faux_device_create_with_groups(const char *name,
> struct device *dev;
> int ret;
>
> + if (IS_ERR_OR_NULL(faux_bus_root))
> + return NULL;
As Greg mentioned, if this happens we already have a much bigger fundamental
problem earlier in the boot process.
Anyway, I think this check only catches when root_device_register() fails, but
everything that comes after root_device_register() in faux_bus_init() still
leaves us with a dangling pointer.
> +
> faux_obj = kzalloc_obj(*faux_obj);
> if (!faux_obj)
> return NULL;
> @@ -234,17 +237,9 @@ int __init faux_bus_init(void)
> {
> int ret;
>
> - faux_bus_root = kzalloc_obj(*faux_bus_root);
> - if (!faux_bus_root)
> - return -ENOMEM;
> -
> - dev_set_name(faux_bus_root, "faux");
> -
> - ret = device_register(faux_bus_root);
> - if (ret) {
> - put_device(faux_bus_root);
> - return ret;
> - }
> + faux_bus_root = root_device_register("faux");
> + if (IS_ERR(faux_bus_root))
> + return PTR_ERR(faux_bus_root);
>
> ret = bus_register(&faux_bus_type);
> if (ret)
> @@ -260,6 +255,6 @@ int __init faux_bus_init(void)
> bus_unregister(&faux_bus_type);
>
> error_bus:
> - device_unregister(faux_bus_root);
> + root_device_unregister(faux_bus_root);
> return ret;
> }
> --
> 2.53.0
next prev parent reply other threads:[~2026-04-24 11:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-24 10:22 [PATCH] driver core: faux: fix root device registration Johan Hovold
2026-04-24 11:23 ` Greg Kroah-Hartman
2026-04-24 11:42 ` Danilo Krummrich [this message]
2026-04-24 14:03 ` Johan Hovold
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=DI1CW4GWGUD6.2K7VZG165WJP8@kernel.org \
--to=dakr@kernel.org \
--cc=driver-core@lists.linux.dev \
--cc=gregkh@linuxfoundation.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=stable@vger.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