From: Greg KH <gregkh@linuxfoundation.org>
To: Shyam Saini <shyamsaini@linux.microsoft.com>
Cc: linux-kernel@vger.kernel.org, linux-modules@vger.kernel.org,
petr.pavlu@suse.com, code@tyhicks.com, linux@rasmusvillemoes.dk,
christophe.leroy@csgroup.eu, hch@infradead.org,
mcgrof@kernel.org, frkaya@linux.microsoft.com,
vijayb@linux.microsoft.com, linux@weissschuh.net,
samitolvanen@google.com, da.gomez@samsung.com, rafael@kernel.org,
dakr@kernel.org, stable@kernel.org
Subject: Re: [PATCH v4 4/4] drivers: base: handle module_kobject creation
Date: Tue, 15 Apr 2025 17:29:46 +0200 [thread overview]
Message-ID: <2025041538-coming-busload-3813@gregkh> (raw)
In-Reply-To: <20250227184930.34163-5-shyamsaini@linux.microsoft.com>
On Thu, Feb 27, 2025 at 10:49:30AM -0800, Shyam Saini wrote:
> module_add_driver() relies on module_kset list for
> /sys/module/<built-in-module>/drivers directory creation.
>
> Since,
> commit 96a1a2412acba ("kernel/params.c: defer most of param_sysfs_init() to late_initcall time")
> drivers which are initialized from subsys_initcall() or any other
> higher precedence initcall couldn't find the related kobject entry
> in the module_kset list because module_kset is not fully populated
> by the time module_add_driver() refers it. As a consequence,
> module_add_driver() returns early without calling make_driver_name().
> Therefore, /sys/module/<built-in-module>/drivers is never created.
>
> Fix this issue by letting module_add_driver() handle module_kobject
> creation itself.
>
> Fixes: 96a1a2412acb ("kernel/params.c: defer most of param_sysfs_init() to late_initcall time")
> Cc: stable@kernel.org
> Suggested-by: Rasmus Villemoes <linux@rasmusvillemoes.dk>
> Signed-off-by: Shyam Saini <shyamsaini@linux.microsoft.com>
> ---
> drivers/base/module.c | 13 +++++--------
> 1 file changed, 5 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/base/module.c b/drivers/base/module.c
> index 5bc71bea883a..218aaa096455 100644
> --- a/drivers/base/module.c
> +++ b/drivers/base/module.c
> @@ -42,16 +42,13 @@ int module_add_driver(struct module *mod, const struct device_driver *drv)
> if (mod)
> mk = &mod->mkobj;
> else if (drv->mod_name) {
> - struct kobject *mkobj;
> -
> - /* Lookup built-in module entry in /sys/modules */
> - mkobj = kset_find_obj(module_kset, drv->mod_name);
> - if (mkobj) {
> - mk = container_of(mkobj, struct module_kobject, kobj);
> + /* Lookup or create built-in module entry in /sys/modules */
> + mk = lookup_or_create_module_kobject(drv->mod_name);
> + if (mk) {
> /* remember our module structure */
> drv->p->mkobj = mk;
> - /* kset_find_obj took a reference */
> - kobject_put(mkobj);
> + /* lookup_or_create_module_kobject took a reference */
> + kobject_put(&mk->kobj);
> }
> }
>
> --
> 2.34.1
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
next prev parent reply other threads:[~2025-04-15 15:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-27 18:49 [PATCH v4 0/4] Properly handle module_kobject creation Shyam Saini
2025-02-27 18:49 ` [PATCH v4 1/4] kernel: param: rename locate_module_kobject Shyam Saini
2025-02-27 18:49 ` [PATCH v4 2/4] kernel: refactor lookup_or_create_module_kobject() Shyam Saini
2025-02-27 18:49 ` [PATCH v4 3/4] kernel: globalize lookup_or_create_module_kobject() Shyam Saini
2025-02-27 18:49 ` [PATCH v4 4/4] drivers: base: handle module_kobject creation Shyam Saini
2025-04-15 15:29 ` Greg KH [this message]
2025-03-05 9:55 ` [PATCH v4 0/4] Properly " Petr Pavlu
2025-03-05 20:01 ` Shyam Saini
2025-03-18 16:23 ` Shyam Saini
2025-04-08 19:19 ` Shyam Saini
2025-04-08 19:21 ` Greg KH
2025-04-16 13:59 ` Petr Pavlu
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=2025041538-coming-busload-3813@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=christophe.leroy@csgroup.eu \
--cc=code@tyhicks.com \
--cc=da.gomez@samsung.com \
--cc=dakr@kernel.org \
--cc=frkaya@linux.microsoft.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=linux@weissschuh.net \
--cc=mcgrof@kernel.org \
--cc=petr.pavlu@suse.com \
--cc=rafael@kernel.org \
--cc=samitolvanen@google.com \
--cc=shyamsaini@linux.microsoft.com \
--cc=stable@kernel.org \
--cc=vijayb@linux.microsoft.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).