| Message ID | 20250211214842.1806521-5-shyamsaini@linux.microsoft.com (mailing list archive) |
|---|---|
| State | New |
| Headers | show |
| Series | Properly handle module_kobject creation | expand |
| Context | Check | Description |
|---|---|---|
| mcgrof/vmtest-modules-next-PR | fail | PR summary |
| mcgrof/vmtest-modules-next-VM_Test-0 | success | Logs for Run CI tests |
| mcgrof/vmtest-modules-next-VM_Test-1 | success | Logs for Run CI tests |
| mcgrof/vmtest-modules-next-VM_Test-2 | fail | Logs for cleanup / Archive results and cleanup |
| mcgrof/vmtest-modules-next-VM_Test-4 | fail | Logs for setup / Setup kdevops environment |
| mcgrof/vmtest-modules-next-VM_Test-3 | fail | Logs for cleanup / Archive results and cleanup |
| mcgrof/vmtest-modules-next-VM_Test-5 | fail | Logs for setup / Setup kdevops environment |
On Tue, Feb 11, 2025 at 01:48:42PM -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") > 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 > Hi, This is the friendly patch-bot of Greg Kroah-Hartman. You have sent him a patch that has triggered this response. He used to manually respond to these common problems, but in order to save his sanity (he kept writing the same thing over and over, yet to different people), I was created. Hopefully you will not take offence and will fix the problem in your patch and resubmit it so that it can be accepted into the Linux kernel tree. You are receiving this message because of the following common error(s) as indicated below: - You have marked a patch with a "Fixes:" tag for a commit that is in an older released kernel, yet you do not have a cc: stable line in the signed-off-by area at all, which means that the patch will not be applied to any older kernel releases. To properly fix this, please follow the documented rules in the Documentation/process/stable-kernel-rules.rst file for how to resolve this. If you wish to discuss this problem further, or you have questions about how to resolve this issue, please feel free to respond to this email and Greg will reply once he has dug out from the pending patches received from other developers. thanks, greg k-h's patch email bot
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); } }
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") 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(-)